Inter-Relay Node Discovery and Measurements

ABSTRACT

During integrated access and backhaul (IAB) node setup, a distributed unit (DU) is configured to transmit synchronization signal blocks (SSBs) for inter-IAB-node discovery and measurement. In parallel to SSB transmission by the DU, user equipment (UEs) and IAB-mobile terminations may be configured to search for and measure on SSBs at specific time instance. In the IAB case, the DU and MT configuration are coordinated to enable inter-node SSB measurements subject to the half-duplex constraint.

CLAIM OF PRIORITY

This application claims priority under 35 U.S.C. § 119(e) to U.S. PatentApplication Ser. No. 62/816,697, filed on Mar. 11, 2019, the entirecontents of which are hereby incorporated by reference.

TECHNICAL FIELD

This disclosure relates generally to wireless communications networks,such as cellular networks. More specifically, this disclosure relates totechniques for discovery of integrated access and backhaul (IAB) nodesfor cellular networks.

BACKGROUND

Wireless communication systems are rapidly growing in usage. Further,wireless communication technology has evolved from voice-onlycommunications to also include the transmission of data, such asInternet and multimedia content, to a variety of devices.

SUMMARY

This disclosure describes methods and systems for transmissionconfigurations for synchronization signal blocks (SSB) and physicalbroadcast channel (PBCH) blocks to support inter-node discovery andmeasurement for integrated access and backhaul (IAB) nodes. Thesetransmission configurations can be also be referred to SSB transmissionconfigurations (STC) and can include SSB-based measurement timingconfiguration (SMTC). In an example, an SMTC window can be used by anIAB node to notify user equipment (UE) or another IAB node (e.g., atarget node) about a periodicity and a timing of the SSBs that the UE ortarget node should use for cell quality measurements. More specifically,this disclosure describes methods and systems for STC and SMTCconfigurations for IAB-node to support inter-IAB-node discovery andmeasurement.

The devices, systems, and processes described in this document provideone or more of the following advantages. The IAB nodes (gNB nodes) canbe used for backhaul operations between and among nodes withoutrequiring a landline backhaul connection between or among the nodes. TheIAB nodes are configured to communicate with one another whilesatisfying the half-duplex constraint. After an IAB node completes aninitial-access stage and the radio resource control (RRC) connection toa parent node is established, a distributed unit (DU) of the IAB nodeinitializes in an operational mode. The DU is configured (e.g., duringthe IAB-node set up) to transmit SSBs for user equipment (UE) cellsearch and measurement as well as for mobile termination (MT) initialcell search. The DU may also be configured to transmit SSB forinter-IAB-node discovery and measurement. in addition to (e.g., inparallel to) SSB transmission by the DU. UEs and IAB-MTs may beconfigured to search for and measure on SSBs at specific time instance.For example, for the IAB, the DU and MT configuration can be coordinatedto enable inter-node SSB measurements subject to a half-duplexconstraint (RDC), which refers to an inability of modems to receive andtransmit data in the same frequency at the same time.

One or more of the following embodiments can implement one or more ofthe foregoing advantages. In a general aspect, a process for operating abase station (BS) includes Obtaining configuration data for a sourceintegrated access and backhaul (IAB) logical radio node (gnB) of thebase station, the configuration data specifying a timing framework forinter-relay gNB discovery and monitoring operations, by the IAB gNB, oftarget IAB gNBs of a cluster. The actions include configuring the sourceIAB gNB, in response to obtaining the configuration data, for asynchronization signal block (SSB) transmission configuration (STC)window for inter-IAB gNB discovery. In some implementations, the SSBcomprises a physical broadcast channel (PBCH) transmission. The actionsinclude configuring the source IAB gNB, in response to obtaining theconfiguration data, for each target IAB gNB of the cluster, for an SSBmonitoring timing configuration (SMTC) window for monitoring that targetIAB gNB. The actions include causing SSB transmission by the source IABgNB in accordance with the STC window and the SMTC window for eachtarget IAB gNB of the cluster.

In some implementations, the configuration data specifies that the STCwindow of the source IAB gNB occurs at a same time as respective SMTCwindows of the target IAB gNBs and each SMTC window of the source IABgNB occurs at the same time that any respective STC window occurs forthe target IAB gNBs.

In some implementations, the STC window and each SMTC window areconfigured within a periodicity of SSB windows for user equipment (UE)access. In some implementations, the cluster comprises three IAB gNBs,including the source IAB gNB and two target IAB gNBs. The two target IABgNBs are configured using the configuration data.

In some implementations, the source IAB gNB of the cluster is configuredto perform STC in a time-orthogonal manner with respect to the targetIAB gNBs of the cluster.

In some implementations, the cluster is a first cluster, where a secondcluster of IAB3 gNBs is configured using identical configuration data asthe configuration data for the first cluster, and the actions includeconfiguring the source IAB gNB to exclude from consideration, within thediscovery and monitoring operations, signals from the IAB gNBs in thesecond cluster.

In some implementations, the actions the STC window is configured inaccordance with an information element indicating a periodicity selectedfrom a list of 80 ms, 160 ms, 320 ms, 640 ms, and 1280 ms and a durationselected from a list of 1, 2, 3, 4, or 5 sub-frames. The SMTC window isconfigured in accordance with indicating a periodicity selected from alist of 80 ms, 160 ms, 320 ms, 640 ms, and 1280 ms and a durationselected from a list of 1, 2, 3, 4, or 5 sub-frames, and where the SMTCwindow is scheduled for each IAB gNB of the cluster.

In a general aspect, a process for operating a base station (BS)includes configuring a first integrated access and backhaul (IAB)logical radio node (gNB) of the cluster for, during a first periodicity:one synchronization signal block (SSB) transmission configuration (STC)window for inter-IAB gNB discovery. The SSB comprises a physicalbroadcast channel (PBCH) transmission. The first IAB node is configuredfor two SSB monitoring timing configuration (SMTC) windows for measuringinter-group IAB gNBs of the cluster. The actions include configuring asecond IAB gNB of the cluster for: two STC windows with respectiveperiodicities for inter-IAB discovery. The second gNB is configured fortwo pairs of SMTC windows with the respective periodicities formeasuring the IAB gNBs in the cluster. The actions include causing SSBtransmission by the first IAB gNB in accordance with the one STC windowsand the two SMTC windows. The actions include causing SSB transmissionby the second IAB gNB in accordance with the two STC windows and the twopairs of SMTC windows.

In some implementations, the IAB gNB is further configured for two SSBwindows for user equipment (UE) access or initial cell search with thefirst periodicity. In some implementations, the first IAB gNB is aneighbor to each other gNB of the cluster. In some implementations, thecluster comprises at least two groups of IAB gNBs in addition to thefirst IAB gNB. The second IAB gNB is included a first group of the atleast two groups of IAB gNBs.

In some implementations, for the second IAB gNB, a first STC window ofthe two STC windows is configured for discovery and measurement of IABgNBs in a second group of the two groups of IAB gNBs, and a second STCwindow of the two STC windows is configured for discovery andmeasurement of other IAB gNBs included in the first group.

In some implementations, for the second IAB gNB, a first pair of SMTCwindows of the two pairs of SMTC windows are configured for measurementof the first IAB gNB and IAB gNBs in a second group of the two groups ofIAB gNBs, and a second pair of SMTC windows of the two pairs of SMTCwindows are configured for measurement of other IAB gNBs included in thefirst group.

In some implementations, any two IAB gNBs in a group of the at least twogroups are not neighboring IAB gNBs in the cluster.

In some implementations, the respective periodicities comprise the firstperiodicity and a second periodicity associated with a smaller frequencythan the first periodicity.

In some implementations, an STC window is configured in accordance withan information element indicating a periodicity selected from a list of80 ms, 160 ms, 320 ms, 640 ms, and 1280 ms and a duration selected froma list of 1, 2, 3, 4, or 5 sub-frames.

In some implementations, an SMTC window is configured in accordance withindicating a periodicity selected from a list of 80 ms, 160 ms, 320 ms,640 ms, and 1280 ms and a duration selected from a list of 1, 2, 3, 4,or 5 sub-frames, and where the SMTC window is scheduled for each IAB gNBof the cluster.

In a general aspect, a BS can include one or more processors and memorystoring instructions that, when executed by the one or more processors,cause the one or more processors to perform actions that includeobtaining configuration data for a source integrated access and backhaul(IAB) logical radio node (gNB) of the base station, the configurationdata specifying a timing framework for inter-relay gNB discovery andmonitoring operations, by the IAB gNB, of target IAB gNBs of a cluster.The actions include configuring the source IAB gNB, in response toobtaining the configuration data, for a synchronization signal block(SSB) transmission configuration (STC) window for inter-IAB gNBdiscovery. In some implementations, the SSB comprises a physicalbroadcast channel (PBCH) transmission. The actions include configuringthe source IAB gNB, in response to obtaining the configuration data, foreach target IAB gNB of the cluster, for an SSB monitoring timingconfiguration (SMTC) window for monitoring that target IAB gNB. Theactions include causing SSB transmission by the source IAB gNB inaccordance with the STC window and the SMTC window for each target IABgNB of the cluster.

In some implementations, the configuration data specifies that the STCwindow of the source IAB gNB occurs at a same time as respective SMTCwindows of the target IAB gNBs and each SMTC window of the source IABgNB occurs at the same time that any respective STC window occurs forthe target IAB gNBs.

In some implementations, the STC window and each SMTC window areconfigured within a periodicity of SSB windows for user equipment (UE)access. In some implementations, the cluster comprises three IAB gNBs,including the source IAB gNB and two target IAB gNBs. The two target IABgNBs are configured using the configuration data.

In some implementations, the source IAB gNB of the cluster is configuredto perform STC in a time-orthogonal manner with respect to the targetIAB gNBs of the cluster.

In some implementations, the cluster is a first cluster, where a secondcluster of IAB gNBs is configured using identical configuration data asthe configuration data for the first cluster, and the actions includeconfiguring the source IAB gNB to exclude from consideration, within thediscovery and monitoring operations, signals from the IAB gNBs in thesecond cluster.

In some implementations, the actions the STC window is configured inaccordance with an information element indicating a periodicity selectedfrom a list of 80 ms, 160 ms, 320 ms, 640 ms, and 1280 ms and a durationselected from a list of 1, 2, 3, 4, or 5 sub-frames. The SMTC window isconfigured in accordance with indicating a periodicity selected from alist of 80 ms, 160 ms, 320 ms, 640 ms, and 1280 ms and a durationselected from a list of 1, 2, 3, 4, or 5 sub-frames, and where the SMTCwindow is scheduled for each IAB gNB of the cluster.

In a general aspect, a BS includes one or more processors and memorystoring instructions that, when executed by the one or more processors,cause the one or more processors to perform actions including a firstintegrated access and backhaul (IAB) logical radio node (gNB) of thecluster for, during a first periodicity: one synchronization signalblock (SSB) transmission configuration (STC) window for inter-IAB gNBdiscovery. The SSB comprises a physical broadcast channel (PBCH)transmission. The first IAB node is configured for two SSB monitoringtiming configuration (SMTC) windows for measuring inter-group IAB gNBsof the cluster. The actions include configuring a second IAB gNB of thecluster for: two STC windows with respective periodicities for inter-IABdiscovery. The second gNB is configured for two pairs of SMTC windowswith the respective periodicities for measuring the IAB gNBs in thecluster. The actions include causing SSB transmission by the first IABgNB in accordance with the one STC windows and the two SMTC windows. Theactions include causing SSB transmission by the second IAB gNB inaccordance with the two STC windows and the two pairs of SMTC windows.

In some implementations, the IAB gNB is further configured for two SSBwindows for user equipment (UE) access or initial cell search with thefirst periodicity. in some implementations, the first IAB gNB is aneighbor to each other gNB of the cluster. In some implementations, thecluster comprises at least two groups of IAB gNBs in addition to thefirst IAB gNB. The second IAB gNB is included a first group of the atleast two groups of IAB gNBs.

In some implementations, for the second IAB gNB, a first STC window ofthe two STC windows is configured for discovery and measurement of IABgNBs in a second group of the two groups of IAB gNBs, and a second STCwindow of the two STC windows is configured for discovery andmeasurement of other IAB gNBs included in the first group.

In some implementations, for the second IAB gNB, a first pair of SMTCwindows of the two pairs of SMTC windows are configured for measurementof the first IAB gNB and IAB gNBs in a second group of the two groups ofIAB gNBs, and a second pair of SMTC windows of the two pairs of SMTCwindows are configured for measurement of other IAB gNBs included in thefirst group.

In some implementations, any two IAB gNBs in a group of the at least twogroups are not neighboring IAB gNBs in the cluster.

In some implementations, the respective periodicities comprise the firstperiodicity and a second periodicity associated with a smaller frequencythan the first periodicity.

In some implementations, an STC window is configured in accordance withan information element indicating a periodicity selected from a list of80 ms, 160 ms, 320 ms, 640 ms, and 1280 ms and a duration selected froma list of 1, 2, 3, 4, or 5 sub-frames.

In some implementations, an SMTC window is configured in accordance withindicating a periodicity selected from a list of 80 ms, 160 ms, 320 ms,640 ms, and 1280 ms and a duration selected from a list of 1, 2, 3, 4,or 5 sub-frames, and where the SMIC window is scheduled for each IAB gNBof the cluster.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features andadvantages will be apparent from the description and drawings, and fromthe claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating an example wireless communicationsystem.

FIGS. 2-3 is a block diagram illustrating an example architecture of asystem including a core network.

FIG. 4 a block diagram illustrating an example of infrastructureequipment that can be included in a base station, user equipment, orboth.

FIG. 5 is a block diagram illustrating an example computer platform thatcan be included in user equipment, an application server, or both.

FIG. 6 is a block diagram illustrating example baseband circuitry andradio front end module circuitry.

FIG. 7 is a block diagram illustrating example cellular communicationcircuitry.

FIG. 8 is a block diagram illustrating example protocol functions forimplementing in a wireless communication device.

FIG. 9 is a block diagram illustrating example components of a corenetwork.

FIG. 10 is a block diagram illustrating a system for executing networkfunctions virtualization (NFV).

FIG. 11 is a block diagram of an example computing system for executingexecutable instructions.

FIG. 12 is a diagram illustrating an example of an integrated access andbackhaul (IAB) network including IAB node-clusters.

FIG. 13 is a diagram showing example measurement timing configurationsfor inter-IAB discovery and measurement.

FIG. 14 is a diagram illustrating an example of an IAB network includingan IAB node-cluster.

FIG. 15 is a diagram showing example measurement timing configurationsfor inter-IAB discovery and measurement in the example node-cluster ofFIG. 14.

FIG. 16 shows examples of definitions for a SSB-TC-Access, aSSB-IC-InterIAB, and a SSB-MIC-InterIAB information element.

FIGS. 17 and 18 illustrate example processes for inter-IAB discovery andmeasurement.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

This disclosure describes methods and systems for transmissionconfigurations for synchronization signal blocks (SSB) and physicalbroadcast channel (PBCH) blocks to support inter-node discovery andmeasurement for integrated access and backhaul (IAB) nodes. Thesetransmission configurations can be also be referred to SSB transmissionconfigurations (STC) and can include SSB-based measurement timingconfiguration (SMTC). In an example, an SMTC window can be used by anIAB node to notify user equipment (UE) or another IAB node (e.g., atarget node) about a periodicity and a timing of the SSBs that the UE ortarget node should use for cell quality measurements. More specifically,this disclosure describes methods and systems for STC and SMTCconfigurations for IAB-node to support inter-IAB-node discovery andmeasurement.

After an IAB node completes an initial-access stage and the radioresource control (RRC) connection to a parent node is established, adistributed unit (DU) of the IAB node initializes in an operationalmode. The DU is configured (e.g., during the IAB-node set up) totransmit SSBs for user equipment (UE) cell search and measurement aswell as for mobile termination (MT) initial cell search. The DU may alsobe configured to transmit SSB for inter-IAB-node discovery andmeasurement. In addition to (e.g., in parallel to) SSB transmission bythe DU, UEs and IAB-MTs may be configured to search for and measure onSSBs at specific time instance. For example, for the IAB, the DU and MTconfiguration can be coordinated to enable inter-node SSB measurementssubject to a half-duplex constraint (HDC), which refers to an inabilityof modems to receive and transmit data in the same frequency at the sametime.

The SSB transmission and measurement configurations for inter-nodemeasurements may be determined in a centralized manner. As a result, theSSB transmission and measurement configurations may be provided by acentral unit (CU). Both IAB nodes and IAB donor nodes are provided withthe SSB transmission configuration by mean of F1 application protocolinterface messages. Generally, for the Release 15 SMTC framework, theSSB periodicity can take different values: (5 ms, 10 ms, 20 ms, 40 ms,80 ms, 160 ms). For IAB nodes, the channel condition is stable. Thus, itmakes sense to allow for even larger SSB periodicities up to 800 ms oreven larger time than 1 s.

Generally, the SSBs for IAB inter-node discovery and measurements can bedefined with a framework using the characteristics of the Release 15SMTC framework with some enhancements. Specifically, a maximum number ofSMTC windows that can be configured for an IAB node, referred asmax(N_(RX)), is at least three (3). In some implementations, max(N_(RX))can be greater than 3. In some implementations, the existing SMTC windowconfiguration can be extended. For example, a system can configure eachSMTC window with its own independent configuration (e.g. periodicity,offset, duration). Additionally, the systems and methods described inthis disclosure introduce SSB transmission configurations (STC)indicating SSB transmission(s).

Generally, there are three example embodiments described to supportextended broadcast channel (BCH) random access channel (RACH) resourceconfigurations to take into account the half-duplex constraints. In afirst embodiment, a system includes a single STC and multiple SMICconfigurations for small IAB-dusters. In this embodiment, 1AB-cluster iscomprised of small number (e.g., 3 or fewer) of IAB-nodes. At least oneIAB node, but typically each IAB-node, is configured with one STC windowfor inter-IAB discovery and measurement. Each IAB node is alsoconfigured for multiple SMTC windows for measuring all neighbor IABnodes in the cluster.

In a third embodiment, a system includes at least one large IAB-clusterincluding multiple STCs and multiple SMTC configurations. In thisembodiment, an IAB-cluster is comprised of relatively large number(e.g., greater than 3) of IAB-nodes. In some implementations, theIAB-nodes inside the cluster can be divided into several groups.Additionally, each IAB-node is configured with multiple STCs and SMTCsto support inter-group and intra-group inter-IAB discovery andmeasurement. Given different channel characteristics, the system canconfigure STCs/STMCs for inner-group and inter-group with differentperiodicities.

In a third embodiment, a system can include SSB-TC-Access,SSB-TC-InterIAB and SSB-MTC-InterIAB Information Element. In thisembodiment, concrete information elements description for SSB-TC-Accessfor UE and IAB-MT initial cell search, SSB-TC-InterIAB for inter-IABdiscovery/measurement and SSB-MTC-InterIAB for measuring neighbor IABsnodes.

A system (e.g., the systems described in relation to FIGS. 1-11, below)can be configured to implement one or more of these embodiments eitherindividually or in any combination. These embodiments are subsequentlydescribed in greater detail with respect to FIGS. 12-17.

FIG. 1 illustrates an example architecture of a system 100 of a network,in accordance with various embodiments. The following description isprovided for an example system 100 that operates in conjunction with thelong-term evolution (LTE) system standards and 5th generation (5G) ornew radio (NR) system standards as provided by third generationpartnership project (3GPP) technical specifications. However, theexample embodiments are not limited in this regard and the describedembodiments may apply to other networks that benefit from the principlesdescribed herein, such as future 3GPP systems Sixth Generation (6G))systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), or the like.

As shown by FIG. 1, the system 100 includes LE 101 a and UE 101 b(collectively referred to as “UEs 101” or “UE 101”). In this example,UEs 101 are illustrated as smartphones (e.g., handheld touchscreenmobile computing devices connectable to one or more cellular networks),but may also comprise any mobile or non-mobile computing device, such asconsumer electronics devices, cellular phones, smartphones, featurephones, tablet computers, wearable computer devices, personal digitalassistants (PDAs), pagers, wireless handsets, desktop computers, laptopcomputers, in-vehicle infotainment (IVI), in-car entertainment (ICE)devices, an instrument cluster (IC), head-up display (HUD) devices,onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobiledata terminals (MDTs), Electronic Engine Management System (EEMS),electronic/engine control units (ECUs), electronic/engine controlmodules (ECMs), embedded systems, microcontrollers, control modules,engine management systems (EMS), networked or “smart” appliances, MTCdevices, M2M, internet of things (IoT) devices, and/or the like.

In some embodiments, any of the UEs 101 may be IoT UEs, which maycomprise a network access layer designed for low-power IoT applicationsutilizing short-lived UE connections. An IoT UE can utilize technologiessuch as machine-to-machine (M2M) or machine-type communications (MTC)for exchanging data with an MTC server or device via a public landmobile network (PLMN), ProSe or device-to-device (D2D) communication,sensor networks, or IoT networks. The M2M or MTC exchange of data may bea machine-initiated exchange of data. An IoT network describesinterconnecting IoT UEs, which may include uniquely identifiableembedded computing devices (within the Internet infrastructure), withshort-lived connections. The IoT UEs may execute background applications(e.g., keep-alive messages, status updates, etc.) to facilitate theconnections of the IoT network.

The UEs 101 may be configured to connect, for example, communicativelycouple, with a radio access network (RAN) 110. In embodiments, the RAN110 may be a next-generation RAN or a 5G RAN, an E-UTRAN, or a legacyRAN, such as an evolved universal-terrestrial RAN (UTRAN) or GERAN. Asused herein, the term “NG RAN” or the like may refer to a RAN 110 thatoperates in an NR or 5G system 100, and the term “E-UTRAN” or the likemay refer to a RAN 110 that operates in an LTE or 4G system 100. The UEs101 utilize connections (or channels) 103 and 104, respectively, each ofwhich comprises a physical communications interface or layer (discussedin further detail below).

In this example, the connections 103 and 104 are illustrated as an airinterface to enable communicative coupling, and can be consistent withcellular communications protocols, such as a GSM protocol, a CDMAnetwork protocol, a PTT protocol, a POC protocol, a UMTS protocol, a3GPP LIE protocol, a 5G protocol, a NR protocol, and/or any of the othercommunications protocols discussed herein. In embodiments, the UEs 101may directly exchange communication data via a ProSe interface 105. TheProSe interface 105 may alternatively be referred to as a SL interface105 and may comprise one or more logical channels, including but notlimited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

The UE 101 b is shown to be configured to access an AP 106 (alsoreferred to as “WLAN node 106,” “WLAN 106,” “WLAN Termination 106,” “WT106” or the like) via connection 107. The connection 107 can comprise alocal wireless connection, such as a connection consistent with any IEEE802.11 protocol, wherein the AP 106 would comprise a wireless fidelity(Wi-Fi®) router. In this example, the AP 106 is shown to be connected tothe Internet without connecting to the core network of the wirelesssystem (described in further detail below). In various embodiments, theUE 101 b, RAN 110, and AP 106 may be configured to utilize LWA operationand/or LWIP operation. The LWA operation may involve the UE 101 b inRRC_CONNFCTED being configured by a RAN node 111 a-b to utilize radioresources of LTE and WLAN, LWIP operation may involve the UE 101 usingWLAN radio resources (e.g., connection 107) via IPsec protocol tunnelingto authenticate and encrypt packets (e.g., IP packets) sent over theconnection 107. IPsec tunneling may include encapsulating the entiretyof original IP packets and adding a new packet header, therebyprotecting the original header of the IP packets.

The RAN 110 can include one or more AN nodes or RAN nodes 111 a and 111b (collectively referred to as “RAN nodes 111” or “RAN node 111”) thatenable the connections 103 and 104. As used herein, the terms “accessnode,” “access point,” or the like may describe equipment that providesthe radio baseband functions for data and/or voice connectivity betweena network and one or more users. These access nodes can be referred toas BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs or TRPs, and so forth,and can comprise ground stations (e.g., terrestrial access points) orsatellite stations providing coverage within a geographic area (e.g., acell). As used herein, the term “NG RAN node” or the like may refer to aRAN node 111 that operates in an NR or 5G system 100 (for example, agNB), and the term “E-UTRAN node” or the like may refer to a RAN node111 that operates in an LTE or 4G system 100 (e.g., an eNB). Accordingto various embodiments, the RAN nodes 111 may be implemented as one ormore of a dedicated physical device such as a macrocell base station,and/or a low power (LP) base station for providing femtocells, picocellsor other like cells having smaller coverage areas, smaller usercapacity, or higher bandwidth compared to macrocells.

In some embodiments, all or parts of the RAN nodes 111 may beimplemented as one or more software entities running on server computersas part of a virtual network, which may be referred to as a CRAN and/ora virtual baseband unit pool (vBBUP). In these embodiments, the CRAN orvBBUP may implement a RAN function split, such as a PDCP split whereinRRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocolentities are operated by individual RAN nodes 111; a MAC/PHY splitwherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN/vBBUPand the PHY layer is operated by individual RAN nodes 111; or a “lowerPHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of thePHY layer are operated by the CRAN/vBBUP and lower portions of the PHYlayer are operated by individual RAN nodes 111. This virtualizedframework allows the freed-up processor cores of the RAN nodes 111 toperform other virtualized applications. In some implementations, anindividual RAN node 111 may represent individual gNB-DUs that areconnected to a gNB-CU via individual F1 interfaces (not shown by FIG.1). In these implementations, the gNB-DUs may include one or more remoteradio heads or RFEMs (see, e.g., FIG. 4), and the gNB-CU may be operatedby a server that is located in the RAN 110 (not shown) or by a serverpool in a similar manner as the CRAN/vBBUP. Additionally oralternatively, one or more of the RAN nodes 111 may be next generationeNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane andcontrol plane protocol terminations toward the UEs 101, and areconnected to a 5GC (e.g., CN 320 of FIG. 3) via an NG interface(discussed infra).

In V2X scenarios one or more of the RAN nodes 111 may be or act as RSUs.The term “Road Side Unit” or “RSU” may refer to any transportationinfrastructure entity used for V2X communications. An RSU may beimplemented in or by a suitable RAN node or a stationary (or relativelystationary) UE, where an RSU implemented in or by a UE may be referredto as a “UE-type RSU,” an RSU implemented in or by an &NB may bereferred to as an “eNB-type RSU,” an RSU implemented in or by a gNB maybe referred to as a “gNB-type RSU,” and the like. In one example, an RSUis a computing device coupled with radio frequency circuitry located ona roadside that provides connectivity support to passing vehicle UEs 101(vUEs 101). The RSU may also include internal data storage circuitry tostore intersection map geometry, traffic statistics, media, as well asapplications/software to sense and control ongoing vehicular andpedestrian traffic. The RSU may operate on the 5.9 GHz Direct ShortRange Communications (DSRC) band to provide very low latencycommunications required for high speed events, such as crash avoidance,traffic warnings, and the like. Additionally or alternatively, the RSUmay operate on the cellular V2X band to provide the aforementioned lowlatency communications, as well as other cellular communicationsservices. Additionally or alternatively, the RSU may operate as a Wi-Fihotspot (2.4 GHz band) and/or provide connectivity to one or morecellular networks to provide uplink and downlink communications. Thecomputing device(s) and some or all of the radiofrequency circuitry ofthe RSU may be packaged in a weatherproof enclosure suitable for outdoorinstallation, and may include a network interface controller to providea wired connection (e.g., Ethernet) to a traffic signal controllerand/or a backhaul network.

Any of the RAN nodes 111 can terminate the air interface protocol andcan be the first point of contact for the UEs 101. In some embodiments,any of the RAN nodes 111 can fulfill various logical functions for theRAN 110 including, but not limited to, radio network controller (RNC)functions such as radio bearer management, uplink and downlink dynamicradio resource management and data packet scheduling, and mobilitymanagement.

In embodiments, the UEs 101 can be configured to communicate using OFDMcommunication signals with each other or with any of the RAN nodes 111over a multicarrier communication channel in accordance with variouscommunication techniques, such as, but not limited to, an OFDMAcommunication technique (e.g., for downlink communications) or a SC-FDMAcommunication technique (e.g., for uplink and ProSe or sidelinkcommunications), although the scope of the embodiments is not limited inthis respect. The OFDM signals can comprise a plurality of orthogonalsubcarriers.

In some embodiments, a downlink resource grid can be used for downlinktransmissions from any of the RAN nodes 111 to the UEs 101, while uplinktransmissions can utilize similar techniques. The grid can be atime-frequency grid, called a resource grid or time-frequency resourcegrid, which is the physical resource in the downlink in each slot. Sucha time-frequency plane representation is a common practice for OFDMsystems, which makes it intuitive for radio resource allocation. Eachcolumn and each row of the resource grid corresponds to one OFDM symboland one OFDM subcarrier, respectively. The duration of the resource gridin the time domain corresponds to one slot in a radio frame. Thesmallest time-frequency unit in a resource grid is denoted as a resourceelement. Each resource grid comprises a number of resource blocks, whichdescribe the mapping of certain physical channels to resource elements.Each resource block comprises a collection of resource elements; in thefrequency domain, this may represent the smallest quantity of resourcesthat currently can be allocated. There are several different physicaldownlink channels that are conveyed using such resource blocks.

According to various embodiments, the UEs 101 and the RAN nodes 111communicate data (for example, transmit and receive) data over alicensed medium (also referred to as the “licensed spectrum” and/or the“licensed band”) and an unlicensed shared medium (also referred to asthe “unlicensed spectrum” and/or the “unlicensed band”). The licensedspectrum may include channels that operate in the frequency range ofapproximately 400 MHz to approximately 3.8 GHz, whereas the unlicensedspectrum may include the 5 GHz band.

To operate in the unlicensed spectrum, the UEs 101 and the RAN nodes 111may operate using LAA, eLAA, and/or feLAA mechanisms. In theseimplementations, the UEs 101 and the RAN nodes 111 may perform one ormore known medium-sensing operations and/or carrier-sensing operationsin order to determine whether one or more channels in the unlicensedspectrum is unavailable or otherwise occupied prior to transmitting inthe unlicensed spectrum. The medium/carrier sensing operations may beperformed according to a listen-before-talk (LBT) protocol.

LBT is a mechanism whereby equipment (for example, UEs 101 RAN nodes111, etc) senses a medium (for example, a channel or carrier frequency)and transmits when the medium is sensed to be idle (or when a specificchannel in the medium is sensed to be unoccupied). The medium sensingoperation may include CCA, which utilizes at least ED to determine thepresence or absence of other signals on a channel in order to determineif a channel is occupied or clear. This LBT mechanism allowscellular/LAA networks to coexist with incumbent systems in theunlicensed spectrum and with other LAA networks. ED may include sensingRF energy across an intended transmission band for a period of time andcomparing the sensed RF energy to a predefined or configured threshold.

Typically, the incumbent systems in the 5 GHz band are WLANs based onIEEE 802.11 technologies. WLAN employs a contention-based channel accessmechanism, called CSMA/CA. Here, when a WLAN node (e.g., a mobilestation (MS) such as UE 101, AP 106, or the like) intends to transmit,the WLAN node may first perform CCA before transmission. Additionally, abackoff mechanism is used to avoid collisions in situations where morethan one WLAN node senses the channel as idle and transmits at the sametime. The backoff mechanism may be a counter that is drawn randomlywithin the CWS, which is increased exponentially upon the occurrence ofcollision and reset to a minimum value when the transmission succeeds.The LBT mechanism designed for LAA is somewhat similar to the CSMA/CA ofWLAN. In some implementations, the LBT procedure for DL or ULtransmission bursts including PDSCH or PUSCH transmissions,respectively, may have an LAA contention window that is variable inlength between X and Y ECCA slots, where X and Y are minimum and maximumvalues for the CWSs for LAA. In one example, the minimum CWS for an LAAtransmission may be 9 microseconds (μs); however, the size of the CWSand a MCOT (for example, a transmission burst) may be based ongovernmental regulatory requirements.

The LAA mechanisms are built upon CA technologies of LTE-Advancedsystems. In CA, each aggregated carrier is referred to as a CC. A CC mayhave a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz and a maximum of fiveCCs can be aggregated, and therefore, a maximum aggregated bandwidth is100 MHz. In FDD systems, the number of aggregated carriers can bedifferent for DL and UL, where the number of UL CCs is equal to or lowerthan the number of DL component carriers. in some cases, individual CCscan have a different bandwidth than other CCs. In TDD systems, thenumber of CCs as well as the bandwidths of each CC is usually the samefor DL and UL.

CA also comprises individual serving cells to provide individual CCs.The coverage of the serving cells may differ, for example, because CCson different frequency bands will experience different pathloss. Aprimary service cell or PCell may provide a PCC for both UL and. DL, andmay handle RRC and NAS related activities. The other serving cells arereferred to as SCells, and each SCell may provide an individual SCC forboth UL and DL. The SCCs may be added and removed as required, whilechanging the PCC may require the UE 101 to undergo a handover. In LAA,eLAA, and feLAA, some or all of the SCells may operate in the unlicensedspectrum (referred to as “LAA SCells”), and the LAA SCells are assistedby a PCell operating in the licensed spectrum. When a UE is configuredwith more than one LAA SCell, the UE may receive UL grants on theconfigured LAA SCells indicating different PUSCH starting positionswithin a same subframe.

The PDSCH carries user data and higher-layer signaling to the UEs 101.The PDCCH carries information about the transport format and resourceallocations related to the PDSCH channel, among other things. It mayalso inform the UEs 101 about the transport format, resource allocation,and HARQ information related to the uplink shared channel. Typically,downlink scheduling (assigning control and shared channel resourceblocks to the UE 101 b within a cell) may be performed at any of the RANnodes 111 based on channel quality information fed back from any of theUEs 101. The downlink resource assignment information may be sent on thePDCCH used for (e.g., assigned to) each of the UEs 101.

The PDCCH uses CCEs to convey the control information. Before beingmapped to resource elements, the PDCCH complex-valued symbols may firstbe organized into quadruplets, which may then be permuted using asub-block interleaver for rate matching. Each PDCCH may be transmittedusing one or more of these CCEs, where each CCE may correspond to ninesets of four physical resource elements known as RFGs. Four QuadraturePhase Shift Keying (QPSK) symbols may be mapped to each RFG. The PDCCHcan be transmitted using one or more CCEs, depending on the size of theDCI and the channel condition. There can be four or more different PDCCHformats defined in LTE with different numbers of CCEs (e.g., aggregationlevel, L=1, 2, 4, or 8).

Some embodiments may use concepts for resource allocation for controlchannel information that are an extension of the above-describedconcepts. For example, some embodiments may utilize an EPDCCH that usesPDSCH resources for control information transmission. The EPDCCH may betransmitted using one or more ECCEs. Similar to above, each ECCE maycorrespond to nine sets of four physical resource elements known asERFGs. An ECCE may have other numbers of ERFGs in some situations.

The RAN nodes 111 may be configured to communicate with one another viainterface 112. In embodiments where the system 100 is an LTE system(e.g., when CN 120 is an EPC 220 as in FIG. 2), the interface 112 may bean X2 interface 112. The X2 interface may be defined between two or moreRAN nodes 111 (e.g., two or more eNBs and the like) that connect to EPC120, and/or between two eNBs connecting to EPC 120. In someimplementations, the X2 interface may include an X2 user plane interface(X2-U) and an X2 control plane interface (X2-C). The X2-U may provideflow control mechanisms for user data packets transferred over the X2interface, and may be used to communicate information about the deliveryof user data between eNBs. For example, the X2-U may provide specificsequence number information for user data transferred from a MeNB to anSeNB; information about successful in sequence delivery of PDCP PDUs toa UE 101 from an SeNB for user data; information of PDCP PDUs that werenot delivered to a UE 101; information about a current minimum desiredbuffer size at the SeNB for transmitting to the UE user data; and thelike. The X2-C may provide intra-LTE access mobility functionality,including context transfers from source to target eNBs, user planetransport control, etc.; load management functionality; as well asinter-cell interference coordination functionality.

In embodiments where the system 100 is a 5G or NR system (e.g., when CN120 is a 5GC 320 as in FIG. 3), the interface 112 may be an Xn interface112. The Xn interface is defined between two or more RAN nodes 11.1(e.g., two or more gNBs and the like) that connect to 5GC 120, between aRAN node 111 (e.g., a gNB) connecting to 5GC 120 and an eNI3, and/orbetween two eNBs connecting to 5GC 120. In some implementations, the Xninterface may include an Xn user plane (Xn-U) interface and an Xncontrol plane (Xn-C) interface. The Xn-U may provide non-guaranteeddelivery of user plane PDUs and support/provide data forwarding and flowcontrol functionality. The Xn-C may provide management and errorhandling functionality, functionality to manage the Xn-C interface;mobility support for UE 101 in a connected mode (e.g., CM-CONNFCTED)including functionality to manage the UE mobility for connected modebetween one or more RAN nodes 111. The mobility support may includecontext transfer from an old (source) serving RAN node 111 to new(target) serving RAN node 111; and control of user plane tunnels betweenold (source) serving RAN node 111 to new (target) serving RAN node 111.A protocol stack of the Xn-U may include a transport network layer builton Internet Protocol (IP) transport layer, and a GTP-U layer on top of aUDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stackmay include an application layer signaling protocol (referred to as XnApplication Protocol (Xn-AP)) and a transport network layer that isbuilt on SCTP. The SCTP may be on top of an IP layer, and may providethe guaranteed delivery of application layer messages. In the transportIP layer, point-to-point transmission is used to deliver the signalingPDUs. In other implementations, the Xn-U protocol stack and/or the Xn-Cprotocol stack may be same or similar to the user plane and/or controlplane protocol stack(s) shown and described herein.

The RAN 110 is shown to be communicatively coupled to a core network inthis embodiment, core network (CN) 120. The CN 120 may comprise aplurality of network elements 122, which are configured to offer variousdata and telecommunications services to customers/subscribers (e.g.,users of UEs 101) who are connected to the CN 120 via the RAN 110. Thecomponents of the CN 120 may be implemented in one physical node orseparate physical nodes including components to read and executeinstructions from a machine-readable or computer-readable medium (e.g.,a non-transitory machine-readable storage medium). In some embodiments,NFV may be utilized to virtualize any or all of the above-describednetwork node functions via executable instructions stored in one or morecomputer-readable storage mediums (described in further detail below). Alogical instantiation of the CN 120 may be referred to as a networkslice, and a logical instantiation of a portion of the CN 120 may bereferred to as a network sub-slice. NFV architectures andinfrastructures may be used to virtualize one or more network functions,alternatively performed by proprietary hardware, onto physical resourcescomprising a combination of industry-standard server hardware, storagehardware, or switches. In other words, NFV systems can be used toexecute virtual or reconfigurable implementations of one or more EPCcomponents/functions.

Generally, the application server 130 may be an element offeringapplications that use IP bearer resources with the core network (e.g.,UMTS PS domain. LTE PS data services, etc.). The application server 130can also be configured to support one or more communication services(e.g., VoIP sessions. PTT sessions, group communication sessions, socialnetworking services, etc.) for the UEs 101 via the EPC 120.

In embodiments, the CN 120 may be a 5GC (referred to as “5GC 120” or thelike), and the RAN 110 may be connected with the CN 120 via an NGinterface 113. In embodiments, the NG interface 113 may be split intotwo parts, an NG user plane (NG-U) interface 114, which carries trafficdata between the RAN nodes 111 and a UPF, and the S1 control plane(NG-C) interface 115, which is a signaling interface between the RANnodes 111 and AMFs. Embodiments where the CN 120 is a 5GC 120 arediscussed in more detail with regard to FIG. 3.

In embodiments, the CN 120 may be a 5G CN (referred to as “5GC 120” orthe like), while in other embodiments, the CN 120 may be an EPC). WhereCN 120 is an EPC (referred to as “EPC 120” or the like), the RAN 110 maybe connected with the CN 120 via an S1 interface 113. In embodiments,the S1 interface 113 may be split into two parts, an S1 user plane(S1-U) interface 114, which carries traffic data between the RAN nodes111 and the S-GW, and the S1-MME interface 115, which is a signalinginterface between the RAN nodes 111 and MMEs.

FIG. 2 illustrates an example architecture of a system 200 including afirst CN 220, in accordance with various embodiments. In this example,system 200 may implement the LIE standard wherein the CN 220 is an EPC220 that corresponds with CN 120 of FIG. 1. Additionally, the UE 201 maybe the same or similar as the UEs 101 of FIG. 1, and the E-UTRAN 210 maybe a RAN that is the same or similar to the RAN 110 of FIG. 1, and whichmay include RAN nodes 111 discussed previously. The CN 220 may compriseMMEs 221, an S-GW 222, a P-GW 223, HSS 224, and a SGSN 225.

The MMEs 221 may be similar in function to the control plane of legacySGSN, and may implement MM functions to keep track of the currentlocation of a UE 201. The MMEs 221 may perform various MM procedures tomanage mobility aspects in access such as gateway selection and trackingarea list management. MM (also referred to as “EPS MM” or “EMM” inE-UTRAN systems) may refer to all applicable procedures, methods, datastorage, etc. that are used to maintain knowledge about a presentlocation of the UE 201, provide user identity confidentiality, and/orperform other like services to users/subscribers. Each UE 201 and theMME 221 may include an MM or EMM sublayer, and an MM context may beestablished in the UE 201 and the MME 221 when an attach procedure issuccessfully completed. The MM context may be a data structure ordatabase object that stores MM-related information of the UE 201. TheMMEs 221 may be coupled with the HSS 224 via an S6a reference point,coupled with the SGSN 225 via an S3 reference point, and coupled withthe S-GW 222 via an S11 reference point.

The SGSN 225 may be a node that serves the UE 201 by tracking thelocation of an individual UE 201 and performing security functions. Inaddition, the SGSN 225 may perform Inter-EPC node signaling for mobilitybetween 2G/3G and E-UTRAN 3GPP access networks; PDN and S-GW selectionas specified by the MMEs 221; handling of UE 201 time zone functions asspecified by the MMEs 221; and MME selection for handovers to E-UTRAN3GPP access network. The S3 reference point between the MMEs 221 and theSGSN 225 may enable user and bearer information exchange for inter-3GPPaccess network mobility in idle and/or active states.

The HSS 224 may comprise a database for network users, includingsubscription-related information to support the network entities'handling of communication sessions. The EPC 220 may comprise one orseveral HSSs 224, depending on the number of mobile subscribers, on thecapacity of the equipment, on the organization of the network, etc. Forexample, the HSS 224 can provide support for routing/roaming,authentication, authorization, naming/addressing resolution, locationdependencies, etc. An S6a reference point between the HSS 224 and theMMEs 221 may enable transfer of subscription and authentication data forauthenticating/authorizing user access to the EPC 220 between HSS 224and the MMEs 221.

The S-GW 222 may terminate the S1 interface 113 (“S1-U” in FIG. 2)toward the RAN 210, and routes data packets between the RAN 210 and theEPC 220. In addition, the S-GW 222 may be a local mobility anchor pointfor inter-RAN node handovers and also may provide an anchor forinter-3GPP mobility. Other responsibilities may include lawfulintercept, charging, and some policy enforcement. The S11 referencepoint between the S-GW 222 and the MMEs 221 may provide a control planebetween the MMEs 221 and the S-GW 222. The S-GW 222 may be coupled withthe P-GW 223 via an S5 reference point.

The P-GW 223 may terminate a SGi interface toward a PDN 230. The P-GW223 may route data packets between the EPC 220 and external networkssuch as a network including the application server 130 (alternativelyreferred to as an “AF”) via an IP interface 125 (see e.g., FIG. 1). Inembodiments, the P-GW 223 may be communicatively coupled to anapplication server (application server 130 of FIG. 1 or PDN 230 in FIG.2) via an IP communications interface 125 (see, e.g., FIG. 1). The S5reference point between the P-GW 223 and the S-GW 222 may provide userplane tunneling and tunnel management between the P-GW 223 and the S-GW222. The S5 reference point may also be used for S-GW 222 relocation dueto UE 201 mobility and if the S-GW 222 needs to connect to anon-collocated P-GW 223 for the required PDN connectivity. The P-GW 223may further include a node for policy enforcement and charging datacollection (e.g., PCEF (not shown)). Additionally, the SGi referencepoint between the P-GW 223 and the packet data network (PDN) 230 may bean operator external public, a private PDN, or an intra operator packetdata network, for example, for provision of IMS services. The P-GW 223may be coupled with a PCRF 226 via a Gx reference point.

PCRF 226 is the policy and charging control element of the EPC 220. In anon-roaming scenario, there may be a single PCRF 226 in the Home PublicLand Mobile Network (HPLMN) associated with a UE 201's Internet ProtocolConnectivity Access Network (IP-CAN) session. In a roaming scenario withlocal breakout of traffic, there may be two PCRFs associated with a UE201's IP-CAN session, a Home PCRF (H-PCRF) within an HPLMN and a VisitedPCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). ThePCRF 226 may be communicatively coupled to the application server 230via the P-GW 223. The application server 230 may signal the PCRF 226 toindicate a new service flow and select the appropriate QoS and chargingparameters. The PCRF 226 may provision this rule into a PCEF (not shown)with the appropriate TFT and QCI, which commences the QoS and chargingas specified by the application server 230. The Gx reference pointbetween the PCRF 226 and the P-GW 223 may allow for the transfer of QoSpolicy and charging rules from the PCRF 226 to PCEF in the P-GW 223. AnRx reference point may reside between the PDN 230 (or “AF 230”) and thePCRF 226.

FIG. 3 illustrates an architecture of a system 300 including a second CN320 in accordance with various embodiments. The system 300 is shown toinclude a UE 301, which may be the same or similar to the UEs 101 and UE201 discussed previously; a (R)AN 310, which may be the same or similarto the RAN 110 and RAN 210 discussed previously, and which may includeRAN nodes 111 discussed previously; and a DN 303, which may be, forexample, operator services, Internet access or 3rd party services; and a5GC 320. The 5GC 320 may include an AUSF 322; an AMF 321; a SMF 324; aNEF 323; a PCF 326; a NRF 325; a UDM 327; an AF 328; a UPF 302; and aNSSF 329.

The UPF 302 may act as an anchor point for intra-RAT and inter-RATmobility, an external PDU session point of interconnect to DN 303, and abranching point to support multi-homed PDU session. The UPF 302 may alsoperform packet routing and forwarding, perform packet inspection,enforce the user plane part of policy rules, lawfully intercept packets(UP collection), perform traffic usage reporting, perform QoS handlingfor a user plane (e.g., packet filtering, gating, UL/DL rateenforcement), perform Uplink Traffic verification (e.g., SDF to QoS flowmapping), transport level packet marking in the uplink and downlink, andperform downlink packet buffering and downlink data notificationtriggering. UPF 302 may include an uplink classifier to support routingtraffic flows to a data network. The DN 303 may represent variousnetwork operator services, Internet access, or third party services. DN303 may include, or be similar to, application server 130 discussedpreviously. The UPF 302 may interact with the SMF 324 via an N4reference point between the SMF 324 and the UPF 302.

The AUSF 322 may store data for authentication of UE 301 and handleauthentication-related functionality. The AUSF 322 may facilitate acommon authentication framework for various access types. The AUSF 322may communicate with the AMF 321 via an N12 reference point between theAMF 321 and the AUSF 322; and may communicate with the UDM 327 via anN13 reference point between the UDM 327 and the AUSF 322. Additionally,the AUSF 322 may exhibit a Nausf service-based interface.

The AMF 321 may be responsible for registration management (e.g., forregistering UE 301, etc.), connection management, reachabilitymanagement, mobility management, and lawful interception of AMF-relatedevents, and access authentication and authorization. The AMF 321 may bea termination point for an N11 reference point between the AMF 321 andthe SNIP 324. The AMF 321 may provide transport for SM messages betweenthe UE 301 and the SMF 324, and act as a transparent proxy for routingSM messages. AMF 321 may also provide transport for SMS messages betweenUE 301 and an SMSF (not shown by FIG. 3). AMF 321 may act as SEAF, whichmay include interaction with the AUSF 322 and the UE 301, receipt of anintermediate key that was established as a result of the UE 301authentication process. Where USIM based authentication is used, the AMF321 may retrieve the security material from the AUSF 322. AMF 321 mayalso include a SCM function, which receives a key from the SEA that ituses to derive access-network specific keys. Furthermore, AMF 321 may bea termination point of a RAN CP interface, which may include or be an N2reference point between the (R)AN 310 and the AMF 321; and the AMF 321may be a termination point of NAS (N1) signaling, and perform NASciphering and integrity protection.

AMF 321 may also support NAS signaling with a UE 301 over an N3IWFinterface. The N3IWF may be used to provide access to untrustedentities. N3IWF may be a termination point for the N2 interface betweenthe (R)AN 310 and the AMF 321 for the control plane, and may be atermination point for the N3 reference point between the (R)AN 310 andthe UPF 302 for the user plane. As such, the AMF 321 may handle N2signaling from the SMF 324 and the AMF 321 for PDU sessions and QoS,encapsulate/de-encapsulate packets for IPSec and N3 tunneling, mark N3user-plane packets in the uplink, and enforce QoS corresponding to N3packet marking taking into account QoS requirements associated with suchmarking received over N2. N3IWF may also relay uplink and downlinkcontrol-plane NAS signaling between the UE 301 and AMF 321 via an N1reference point between the UE 301 and the AMF 321, and relay uplink anddownlink user-plane packets between the UE 301 and UPF 302. The N3IWFalso provides mechanisms for IPsec tunnel establishment with the UE 301.The AMF 321 may exhibit a Namf service-based interface, and may be atermination point for an N14 reference point between two AMFs 321 and anN17 reference point between the AMF 321 and a 5G-EIR (not shown by FIG.3).

The UE 301 may need to register with the AMF 321 in order to receivenetwork services. RM is used to register or deregister the UE 301 withthe network (e.g., AMF 321), and establish a UE context in the network(e.g., AMF 321). The UE 301 may operate in an RM-RFGISTERFD state or anRM-DERFGISTERFD state. In the RM-DERFGISTERFD state, the UE 301 is notregistered with the network, and the UE context in AMF 321 holds novalid location or routing information for the UE 301 so the UE 301 isnot reachable by the AMF 321. In the RM-RFGISTERFD state, the UE 301 isregistered with the network, and the UE context in AMF 321 may hold avalid location or routing information for the UE 301 so the UE 301 isreachable by the AMF 321. In the RM-RFGISTERFD state, the UE 301 mayperform mobility Registration Update procedures, perform periodicRegistration Update procedures triggered by expiration of the periodicupdate timer (e.g., to notify the network that the UE 301 is stillactive), and perform a Registration Update procedure to update UEcapability information or to re-negotiate protocol parameters with thenetwork, among others.

The AMF 321 may store one or more RM contexts for the UE 301, where eachRM context is associated with a specific access to the network. The RMcontext may be a data structure, database object, etc. that indicates orstores, inter alia, a registration state per access type and theperiodic update timer. The AMF 321 may also store a 5GC MM context thatmay be the same or similar to the (E)MM context discussed previously. Invarious embodiments, the AMF 321 may store a CE mode B Restrictionparameter of the UE 301 in an associated MM context or RM context. TheAMF 321 may also derive the value, when needed, from the UE's usagesetting parameter already stored in the UE context (and/or MM/RMcontext).

CM may be used to establish and release a signaling connection betweenthe UE 301 and the AMF 321 over the N1 interface. The signalingconnection is used to enable NAS signaling exchange between the UE 301and the CN 320, and comprises both the signaling connection between theUE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPPaccess) and the N2 connection for the UE 301 between the AN (e.g., RAN310) and the AMF 321. The UE 301 may operate in one of two CM states,CM-IDLE mode or CM-CONNFCTED mode. When the UE 301 is operating in theCM-IDLE state/mode, the UE 301 may have no NAS signaling connectionestablished with the AMF 321 over the N1 interface, and there may be(R)AN 310 signaling connection (e.g., N2 and/or N3 connections) for theUE 301. When the UE 301 is operating in the CM-CONNFCTED state/mode, theUE 301 may have an established NAS signaling connection with the AMF 321over the N1 interface, and there may be a (R)AN 310 signaling connection(e.g., N2 and/or N3 connections) for the UE 301. Establishment of an N2connection between the (R)AN 310 and the AMF 321 may cause the UE 301 totransition from CM-IDLE mode to CM-CONNFCTED mode, and the UE 301 maytransition from the CM-CONNFCTED mode to the CM-IDLE, mode when N2signaling between the (R)AN 310 and the AMF 321 is released.

The SMF 324 may be responsible for SM (e.g., session establishment,modify and release, including tunnel maintain between UPF and AN node);UE IP address allocation and management (including optionalauthorization); selection and control of UP function; configuringtraffic steering at UPF to route traffic to proper destination;termination of interfaces toward policy control functions; controllingpart of policy enforcement and QoS; lawful intercept (for SM events andinterface to LI system); termination of SM parts of NAS messages;downlink data notification; initiating AN specific SM information, sentvia AMF over N2 to AN; and determining SSC mode of a session SM mayrefer to management of a PDU session, and a PDU session or “session” mayrefer to a PDU connectivity service that provides or enables theexchange of PDUs between a UE 301 and a data network (DN) 303 identifiedby a Data Network Name (DNN). PDU sessions may be established upon UE301 request, modified upon UE 301 and 5GC 320 request, and released uponUE 301 and 5GC 320 request using NAS SM signaling exchanged over the N1reference point between the UE 301 and the SMF 324. Upon request from anapplication server, the 5GC 320 may trigger a specific application inthe UE 301. In response to receipt of the trigger message, the UE 301may pass the trigger message (or relevant parts/information of thetrigger message) to one or more identified applications in the UE 301.The identified application(s) in the UE 301 may establish a PDU sessionto a specific DNN. The SMF 324 may check whether the UE 301 requests arecompliant with user subscription information associated with the UE 301.In this regard, the SMF 324 may retrieve and/or request to receiveupdate notifications on SMF 324 level subscription data from the UDM327.

The SMF 324 may include the following roaming functionality: handlinglocal enforcement to apply QoS SLAs (VPLMN); charging data collectionand charging interface (VPLMN); lawful intercept (in VPLMN for SM eventsand interface to LI system); and support for interaction with externalDN for transport of signaling for PDU sessionauthorization/authentication by external DN. An N16 reference pointbetween two SMFs 324 may be included in the system 300, which may bebetween another SMF 324 in a visited network and the SMF 324 in the homenetwork in roaming scenarios. Additionally, the SMF 324 may exhibit theNsmf service-based interface.

The NEF 323 may provide means for securely exposing the services andcapabilities provided by 3GPP network functions for third party,internal exposure/re-exposure. Application Functions (e.g., AF 328),edge computing or fog computing systems, etc. In such embodiments, theNEF 323 may authenticate, authorize, and/or throttle the AFs. NEF 323may also translate information exchanged with the AF 328 and informationexchanged with internal network functions. For example, the NEF 323 maytranslate between an AF-Service-Identifier and an internal 5GCinformation. NEF 323 may also receive information from other networkfunctions (NFs) based on exposed capabilities of other networkfunctions. This information may be stored at the NEF 323 as structureddata, or at a data storage NF using standardized interfaces. The storedinformation can then be re-exposed by the NEF 323 to other NFs and AFs,and/or used for other purposes such as analytics. Additionally, the NEF323 may exhibit a Nnef service-based interface.

The NRF 325 may support service discovery functions, receive NFdiscovery requests from NF instances, and provide the information of thediscovered NF instances to the NF instances. NRF 325 also maintainsinformation of available NF instances and their supported services. Asused herein, the terms “instantiate,” “instantiation,” and the like mayrefer to the creation of an instance, and an “instance” may refer to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code. Additionally, the NRF 325 may exhibit theNnrf service-based interface.

The PCF 326 may provide policy rules to control plane function(s) toenforce them, and may also support unified policy framework to governnetwork behavior. The PCF 326 may also implement an FE to accesssubscription information relevant for policy decisions in a UDR of theUDM 327. The PCF 326 may communicate with the AMF 321 via an N15reference point between the PCF 326 and the AMF 321, which may include aPCF 326 in a visited network and the AMF 321 in case of roamingscenarios. The PCF 326 may communicate with the AF 328 via an N5reference point between the PCF 326 and the AF 328 and with the SMF 324via an N7 reference point between the PCF 326 and the SMF 324. Thesystem 300 and/or CN 320 may also include an N24 reference point betweenthe PCF 326 (in the home network) and a PCF 326 in a visited network.Additionally, the PCF 326 may exhibit an Npcf service-based interface.

The UDM 327 may handle subscription-related information to support thenetwork entities' handling of communication sessions, and may storesubscription data of UE 301. For example, subscription data may becommunicated between the UDM 327 and the AMF 321 via an N8 referencepoint between the UDM 327 and the AMF. The UDM 327 may include twoparts, an application FE and a UDR (the FE and UDR are not shown by FIG.3). The UDR may store subscription data and policy data for the UDM 327and the PCF 326, and/or structured data for exposure and applicationdata (including PFDs for application detection, application requestinformation for multiple UEs 301) for the NEF 323. The Nudrservice-based interface may be exhibited by the UDR 221 to allow the UDM327, PCF 326, and NEF 323 to access a particular set of the stored data,as well as to read, update (e.g., add, modify), delete, and subscribe tonotification of relevant data changes in the UDR. The UDM may include aUDM-FE, which is in charge of processing credentials, locationmanagement, subscription management, and so on. Several different frontends may serve the same user in different transactions. The UDM-FEaccesses subscription information stored in the UDR and performsauthentication credential processing, user identification handling,access authorization, registration/mobility management, and subscriptionmanagement. The UDR may interact with the SMF 324 via an N10 referencepoint between the UDM 327 and the SMF 324, UDM 327 may also support SMSmanagement, wherein an SMS-FE implements the similar application logicas discussed previously. Additionally, the UDM 327 may exhibit the Nudmservice-based interface.

The AF 328 may provide application influence on traffic routing, provideaccess to the NCE, and interact with the policy framework for policycontrol. The NCE may be a mechanism that allows the 5GC 320 and AF 328to provide information to each other via NEF 323, which may be used foredge computing implementations. In such implementations, the networkoperator and third party services may be hosted close to the UE 301access point of attachment to achieve an efficient service deliverythrough the reduced end-to-end latency and load on the transportnetwork. For edge computing implementations, the 5GC may select a UPF302 close to the UE 301 and execute traffic steering from the UPF 302 toDN 303 via the N6 interface. This may be based on the UE subscriptiondata, UE location, and information provided by the AF 328. In this way,the AF 328 may influence UPF (re)selection and traffic routing. Based onoperator deployment, when AF 328 is considered to be a trusted entity,the network operator may permit AF 328 to interact directly withrelevant NFs. Additionally, the AF 328 may exhibit a Naf service-basedinterface.

The NSSF 329 may select a set of network slice instances serving the UE301. The NSSF 329 may also determine allowed NSSAI and the mapping tothe subscribed S-NSSAIs, if needed. The NSSF 329 may also determine theAMF set to be used to serve the UE 301, or a list of candidate AMF(s)321 based on a suitable configuration and possibly by querying the NRF325. The selection of a set of network slice instances for the UE 301may be triggered by the AMF 321 with which the UE 301 is registered byinteracting with the NSSF 329, which may lead to a change of AMF 321.The NSSF 329 may interact with the AMF 321 via an N22 reference pointbetween AMF 321 and NSSF 329; and may communicate with another NSSF 329in a visited network via an N31 reference point (not shown by FIG. 3).Additionally, the NSSF 329 may exhibit an Nnssf service-based interface.

As discussed previously, the CN 320 may include an SMSF, which may beresponsible for SMS subscription checking and verification, and relayingSM messages to/from the UE 301 to/from other entities, such as anSMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF 321 andUDM 327 for a notification procedure that the UE 301 is available forSMS transfer (e.g., set a UE not reachable flag, and notifying UDM 327when UE 301 is available for SMS).

The CN 120 may also include other elements that are not shown by FIG. 3,such as a Data Storage system/architecture, a 5G-EIR, a SEPP, and thelike. The Data Storage system may include a SDSF, an UDSF, and/or thelike. Any NF may store and retrieve unstructured data into/from the UDSF(e.g., UE contexts), via N18 reference point between any NF and the UDSF(not shown by FIG. 3). Individual NFs may share a UDSF for storing theirrespective unstructured data or individual NFs may each have their ownUDSF located at or near the individual NFs. Additionally, the UDSF mayexhibit a Nudsf service-based interface (not shown by FIG. 3). The5G-EIR may be an NF that checks the status of PEI for determiningwhether particular equipment/entities are blacklisted from the network;and the SEPP may be a non-transparent proxy that performs topologyhiding, message filtering, and policing on inter-PLMN control planeinterfaces.

Additionally, there may be many more reference points and/orservice-based interfaces between the NF services in the NFs; however,these interfaces and reference points have been omitted from FIG. 3 forclarity. In one example, the CN 320 may include an Nx interface, whichis an inter-CN interface between the MME (e.g., MME 221) and the AMF 321in order to enable interworking between CN 320 and CN 220. Other exampleinterfaces/reference points may include an N5g-EIR service-basedinterface exhibited by a 5G-EIR, an N27 reference point between the NRFin the visited network and the NRF in the home network; and an N31reference point between the NSSF in the visited network and the NSSF inthe home network.

FIG. 4 illustrates an example of infrastructure equipment 400 inaccordance with various embodiments. The infrastructure equipment 400(or “system 400”) may be implemented as a base station, radio head, RANnode such as the RAN nodes 111 and/or AP 106 shown and describedpreviously, application server(s) 130, and/or any other element/devicediscussed herein. In other examples, the system 400 could be implementedin or by a UE.

The system 400 includes application circuitry 405, baseband circuitry410, one or more radio front end modules (RFEMs) 415, memory circuitry420, power management integrated circuitry (PMIC) 425, power teecircuitry 430, network controller circuitry 435, network interfaceconnector 440, satellite positioning circuitry 445, and user interface450. In some embodiments, the device 400 may include additional elementssuch as, for example, memory/storage, display, camera, sensor, orinput/output (I/O) interface. In other embodiments, the componentsdescribed below may be included in more than one device. For example,said circuitries may be separately included in more than one device forCRAN, vBBU, or other like implementations.

Application circuitry 405 includes circuitry such as, but not limited toone or more processors (or processor cores), cache memory, and one ormore of low drop-out voltage regulators (LDOs), interrupt controllers,serial interfaces such as SPI, I2C or universal programmable serialinterface module, real time clock (RTC), timer-counters includinginterval and watchdog timers, general purpose input/output (I/O or IO),memory card controllers such as Secure Digital (SD) MultiMediaCard (MMC)or similar, Universal Serial Bus (USB) interfaces, Mobile IndustryProcessor Interface (MIPI) interfaces and Joint Test Access Group (JTAG)test access ports. The processors (or cores) of the applicationcircuitry 405 may be coupled with or may include memory/storage elementsand may be configured to execute instructions stored in thememory/storage to enable various applications or operating systems torun on the system 400. In some implementations, the memory/storageelements may be on-chip memory circuitry, which may include any suitablevolatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM,Flash memory, solid-state memory, and/or any other type of memory devicetechnology, such as those discussed herein.

The processor(s) of application circuitry 405 may include, for example,one or more processor cores (CPUs), one or more application processors,one or more graphics processing units (GPUs), one or more reducedinstruction set computing (RISC) processors, one or more Acorn RISCMachine (ARM) processors, one or more complex instruction set computing(CISC) processors, one or more digital signal processors (DSP), one ormore FPGAs, one or more PLDs, one or more ASTCs, one or moremicroprocessors or controllers, or any suitable combination thereof. Insome embodiments, the application circuitry 405 may comprise, or may be,a special-purpose processor/controller to operate according to thevarious embodiments herein. As examples, the processor(s) of applicationcircuitry 405 may include one or more Intel Pentium®, Core®, or Xeon®processor(s); Advanced Micro Devices (AMD) Ryzen® processor(s),Accelerated Processing Units (APUs), or Epyc® processors; ARM-basedprocessor(s) licensed from ARM Holdings, Ltd. such as the ARM Cortex-Afamily of processors and the ThunderX2® provided by Cavium™, Inc.; aMIPS-based design from MIPS Technologies, Inc. such as MIPS WarriorP-class processors; and/or the like. In some embodiments, the system 400may not utilize application circuitry 405, and instead may include aspecial-purpose processor/controller to process IP data received from anEPC or 5GC, for example.

In some implementations, the application circuitry 405 may include oneor more hardware accelerators, which may be microprocessors,programmable processing devices, or the like. The one or more hardwareaccelerators may include, for example, computer vision (CV) and/or deeplearning (DL) accelerators. As examples, the programmable processingdevices may be one or more a field-programmable devices (FPDs) such asfield-programmable gate arrays (FPGAs) and the like; programmable logicdevices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs(HCPLDs), and the like; ASICs such as structured ASTCs and the like;programmable SoCs (PSoCs); and the like. In such implementations, thecircuitry of application circuitry 405 may comprise logic blocks orlogic fabric, and other interconnected resources that may be programmedto perform various functions, such as the procedures, methods,functions, etc. of the various embodiments discussed herein. In suchembodiments, the circuitry of application circuitry 405 may includememory cells (e.g., erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), flashmemory, static memory (e.g., static random access memory (SRAM),anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc.in look-up-tables (LUTs) and the like.

The baseband circuitry 410 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Thevarious hardware electronic elements of baseband circuitry 410 arediscussed infra with regard to FIG. 6.

User interface circuitry 450 may include one or more user interfacesdesigned to enable user interaction with the system 400 or peripheralcomponent interfaces designed to enable peripheral component interactionwith the system 400. User interfaces may include, but are not limitedto, one or more physical or virtual buttons (e.g., a reset button), oneor more indicators (e.g., light emitting diodes (LEDs)), a physicalkeyboard or keypad, a mouse, a touchpad, a touchscreen, speakers orother audio emitting devices, microphones, a printer, a scanner, aheadset, a display screen or display device, etc. Peripheral componentinterfaces may include, but are not limited to, a nonvolatile memoryport, a universal serial bus (USB) port, an audio jack, a power supplyinterface, etc.

The radio front end modules (RFEMs) 415 may comprise a millimeter wave(mmWave) RFEM and one or more sub-mmWave radio frequency integratedcircuits (RFICs). In some implementations, the one or more sub-mmWaveRFICs may be physically separated from the mmWave RFEM. The RFICs mayinclude connections to one or more antennas or antenna arrays (see e.g.,antenna array 611 of FIG. 6 infra), and the RFEM may be connected tomultiple antennas. In alternative implementations, both mmWave andsub-mmWave radio functions may be implemented in the same physical RFEM415, which incorporates both mmWave antennas and sub-mmWave.

The memory circuitry 420 may include one or more of volatile memoryincluding dynamic random access memory (DRAM) and/or synchronous dynamicrandom access memory (SDRAM), and nonvolatile memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), magnetoresistiverandom access memory (MRAM), etc., and may incorporate thethree-dimensional (3D) cross-point (XPOINT) memories from Intel® andMicron®. Memory circuitry 420 may be implemented as one or more ofsolder down packaged integrated circuits, socketed memory modules andplug-in memory cards.

The PMIC 425 may include voltage regulators, surge protectors, poweralarm detection circuitry, and one or more backup power sources such asa battery or capacitor. The power alarm detection circuitry may detectone or more of brown out (under-voltage) and surge (over-voltage)conditions. The power tee circuitry 430 may provide for electrical powerdrawn from a network cable to provide both power supply and dataconnectivity to the infrastructure equipment 400 using a single cable.

The network controller circuitry 435 may provide connectivity to anetwork using a standard network interface protocol such as Ethernet,Ethernet over GRF Tunnels, Ethernet over Multiprotocol Label Switching(MPLS), or some other suitable protocol. Network connectivity may beprovided to/from the infrastructure equipment 400 via network interfaceconnector 440 using a physical connection, which may be electrical(commonly referred to as a “copper interconnect”), optical, or wireless.The network controller circuitry 435 may include one or more dedicatedprocessors and/or FPGAs to communicate using one or more of theaforementioned protocols. In some implementations, the networkcontroller circuitry 435 may include multiple controllers to provideconnectivity to other networks using the same or different protocols.

The positioning circuitry 445 includes circuitry to receive and decodesignals transmitted/broadcasted by a positioning network of a globalnavigation satellite system (GNSS). Examples of navigation satelliteconstellations (or GNSS) include United States' Global PositioningSystem (GPS), Russia's Global Navigation System (GLONASS), the EuropeanUnion's Galileo system, China's BeiDou Navigation Satellite System, aregional navigation system or GNSS augmentation system (e.g., Navigationwith Indian Constellation (NAVIC), Japan's Quasi-Zenith Satellite System(QZSS), France's Doppler Orbitography and Radio-positioning Integratedby Satellite (DORIS), etc.), or the like. The positioning circuitry 445comprises various hardware elements (e.g., including hardware devicessuch as switches, filters, amplifiers, antenna. elements, and the liketo facilitate OTA communications) to communicate with components of apositioning network, such as navigation satellite constellation nodes.In some embodiments, the positioning circuitry 445 may include aMicro-Technology for Positioning, Navigation, and Timing (Micro-PNT) ICthat uses a master timing clock to perform position tracking/estimationwithout GNSS assistance. The positioning circuitry 445 may also be partof, or interact with, the baseband circuitry 410 and/or RFEMs 415 tocommunicate with the nodes and components of the positioning network.The positioning circuitry 445 may also provide position data and/or timedata to the application circuitry 405, which may use the data tosynchronize operations with various infrastructure (e.g., RAN nodes 111,etc.), or the like.

The components shown by FIG. 4 may communicate with one another usinginterface circuitry, which may include any number of bus and/orinterconnect (IX) technologies such as industry standard architecture(ISA), extended ISA (EISA), peripheral component interconnect (PCI),peripheral component interconnect extended (PCIx), PCI express (PCIe),or any number of other technologies. The bus/IX may be a proprietarybus, for example, used in a SoC based system. Other bus/IX systems maybe included, such as an I2C interface, an SPI interface, point to pointinterfaces, and a power bus, among others.

FIG. 5 illustrates an example of a platform 500 (or “device 500”) inaccordance with various embodiments. In embodiments, the computerplatform 500 may be suitable for use as UEs 101, 201, 301, applicationservers 130, and/or any other element/device discussed in this document.The platform 500 may include any combinations of the components shown inthe example. The components of platform 500 may be implemented asintegrated circuits (ICs), portions thereof, discrete electronicdevices, or other modules, logic, hardware, software, firmware, or acombination thereof adapted in the computer platform 500, or ascomponents otherwise incorporated within a chassis of a larger system.The block diagram of FIG. 5 is intended to show a high level view ofcomponents of the computer platform 500. However, some of the componentsshown may be omitted, additional components may be present, anddifferent arrangement of the components shown may occur in otherimplementations.

Application circuitry 505 includes circuitry such as, but not limited toone or more processors (or processor cores), cache memory, and one ormore of LDOs, interrupt controllers, serial interfaces such as SPI, I2Cor universal programmable serial interface module, RTC, timer-countersincluding interval and watchdog timers, general purpose I/O, memory cardcontrollers such as SD MMC or similar, USB interfaces, MIPI interfaces,and JTAG test access ports. The processors (or cores) of the applicationcircuitry 505 may be coupled with or may include memory/storage elementsand may be configured to execute instructions stored in thememory/storage to enable various applications or operating systems torun on the system 500. In some implementations, the memory/storageelements may be on-chip memory circuitry, which may include any suitablevolatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM,Flash memory, solid-state memory, and/or any other type of memory devicetechnology, such as those discussed in this document.

The processor(s) of application circuitry 405 may include, for example,one or more processor cores, one or more application processors, one ormore GPUs, one or more RISC processors, one or more ARM processors, oneor more CISC processors, one or more DSP, one or more FPGAs, one or morePLDs, one or more ASTCs, one or more microprocessors or controllers, amultithreaded processor, an ultra-low voltage processor, an embeddedprocessor, some other known processing element, or any suitablecombination thereof. In some embodiments, the application circuitry 405may comprise, or may be, a special-purpose processor/controller tooperate according to the various embodiments in this document.

As examples, the processor(s) of application circuitry 505 may includean Intel® Architecture Core™ based processor, such as a Quark™, anAtom™, an i3, an i5, an i7, or an MCU-class processor, or another suchprocessor available from Intel® Corporation, Santa Clara, Calif. Theprocessors of the application circuitry 505 may also be one or more ofAdvanced Micro Devices (AMD) Ryzen® processor(s) or AcceleratedProcessing Units (APUs); A5-A9 processor(s) from Apple® Inc.,Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., TexasInstruments, Inc.® Open Multimedia Applications Platform (OMAP)™processor(s); a MIPS-based design from MIPS Technologies, Inc, such asMIPS Warrior M-class, Warrior I-class, and Warrior P-class processors;an ARM-based design licensed from ARM Holdings, Ltd., such as the ARMCortex-A, Cortex-R, and Cortex-M family of processors; or the like. Insome implementations, the application circuitry 505 may be a part of asystem on a chip (SoC) in which the application circuitry 505 and othercomponents are formed into a single integrated circuit, or a singlepackage, such as the Edison™ or Galileo™ SoC boards from Intel®Corporation.

Additionally or alternatively, application circuitry 505 may includecircuitry such as, but not limited to, one or more a field-programmabledevices (FPDs) such as FPGAs and the like; programmable logic devices(PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), andthe like; ASTCs such as structured ASICs and the like; programmable SoCs(PSoCs); and the like. In such embodiments, the circuitry of applicationcircuitry 505 may comprise logic blocks or logic fabric, and otherinterconnected resources that may be programmed to perform variousfunctions, such as the procedures, methods, functions, etc. of thevarious embodiments discussed in this document. In such embodiments, thecircuitry of application circuitry 505 may include memory cells (e.g.,erasable programmable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), flash memory, static memory(e.g., static random access memory (SRAM), anti-fuses, etc.)) used tostore logic blocks, logic fabric, data, etc. in look-up tables (LUTs)and the like.

The baseband circuitry 510 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Thevarious hardware electronic elements of baseband circuitry 510 arediscussed infra with regard to FIG. 6.

The RFEMs 515 may comprise a millimeter wave (mmWave) RFEM and one ormore sub-mmWave radio frequency integrated circuits (RFICs). In someimplementations, the one or more sub-mmWave RFICs may be physicallyseparated from the mmWave RFEM. The RFICs may include connections to oneor more antennas or antenna arrays (see e.g., antenna array 611 of FIG.6 infra), and the RFEM may be connected to multiple antennas. Inalternative implementations, both mmWave and sub-mmWave radio functionsmay be implemented in the same physical RFEM 515, which incorporatesboth mmWave antennas and sub-mmWave.

The memory circuitry 520 may include any number and type of memorydevices used to provide for a given amount of system memory. Asexamples, the memory circuitry 520 may include one or more of volatilememory including random access memory (RAM), dynamic RAM (DRAM) and/orsynchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), magnetoresistiverandom access memory (MRAM), etc. The memory circuitry 520 may bedeveloped in accordance with a Joint Electron Devices EngineeringCouncil (JEDEC) low power double data rate (LPDDR)-based design, such asLPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry 520 may beimplemented as one or more of solder down packaged integrated circuits,single die package (SDP), dual die package (DDP) or quad die package(Q17P), socketed memory modules, dual inline memory modules (DIMMs)including microDIMMs or MiniDIMMs, and/or soldered onto a motherboardvia a ball grid array (BGA). In low power implementations, the memorycircuitry 520 may be on-die memory or registers associated with theapplication circuitry 505. To provide for persistent storage ofinformation such as data, applications, operating systems and so forth,memory circuitry 520 may include one or more mass storage devices, whichmay include, inter alia, a solid state disk drive (SSDD), hard diskdrive (HDD), a micro HDD, resistance change memories, phase changememories, holographic memories, or chemical memories, among others. Forexample, the computer platform 500 may incorporate the three-dimensional(3D) cross-point (XPOINT) memories from Intel® and Micron®.

Removable memory circuitry 523 may include devices, circuitry,enclosures/housings, ports or receptacles, etc. used to couple portabledata storage devices with the platform 500. These portable data storagedevices may be used for mass storage purposes, and may include, forexample, flash memory cards (e.g., Secure Digital (SD) cards, microSDcards, xD picture cards, and the like), and USB flash drives, opticaldiscs, external HDDs, and the like.

The platform 500 may also include interface circuitry (not shown) thatis used to connect external devices with the platform 500. The externaldevices connected to the platform 509 via the interface circuitryinclude sensor circuitry 521 and electro-mechanical components (EMCs)522, as well as removable memory devices coupled to removable memorycircuitry 523.

The sensor circuitry 521 include devices, modules, or subsystems whosepurpose is to detect events or changes in its environment and send theinformation (sensor data) about the detected events to some other adevice, module, subsystem, etc. Examples of such sensors include, interalia, inertia measurement units (IMUs) comprising accelerometers,gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS)or nanoelectromechanical systems (NEMS) comprising 3-axisaccelerometers, 3-axis gyroscopes, and/or magnetometers; level sensors;flow sensors; temperature sensors (e.g., thermistors); pressure sensors;barometric pressure sensors; gravimeters; altimeters; image capturedevices (e.g., cameras or lens-less apertures); light detection andranging (LiDAR) sensors; proximity sensors (e.g., infrared radiationdetector and the like), depth sensors, ambient light sensors, ultrasonictransceivers; microphones or other like audio capture devices; etc.

EMCs 522 include devices, modules, or subsystems whose purpose is toenable platform 500 to change its state, position, and/or orientation,or move or control a mechanism or (sub)system. Additionally, EMCs 522may be configured to generate and send messages/signaling, to othercomponents of the platform 500 to indicate a current state of the EMCs522. Examples of the EMCs 522 include one or more power switches, relaysincluding electromechanical relays (EMRs) and/or solid state relays(SSRs), actuators (e.g., valve actuators, etc.), an audible soundgenerator, a visual warning device, motors (e.g., DC motors, steppermotors, etc.), wheels, thrusters, propellers, claws, clamps, hooks,and/or other like electro-mechanical components. In embodiments,platform 500 is configured to operate one or more EMCs 522 based on oneor more captured events and/or instructions or control signals receivedfrom a service provider and/or various clients.

In some implementations, the interface circuitry may connect theplatform 500 with positioning circuitry 545. The positioning circuitry545 includes circuitry to receive and decode signalstransmitted/broadcasted by a positioning network of a GNSS. Examples ofnavigation satellite constellations (or GNSS) include United States'GPS, Russia's GLONASS, the European Union's Galileo system, China'sBeiDou Navigation Satellite System, a regional navigation system or GNSSaugmentation system (e.g., NAVIC), Japan's QZSS, France's DORIS, etc.),or the like. The positioning circuitry 545 comprises various hardwareelements (e.g., including hardware devices such as switches, filters,amplifiers, antenna elements, and the like to facilitate OTAcommunications) to communicate with components of a positioning network,such as navigation satellite constellation nodes. In some embodiments,the positioning circuitry 545 may include a Micro-PNT IC that uses amaster timing clock to perform position tracking/estimation without GNSSassistance. The positioning circuitry 545 may also be part of, orinteract with, the baseband circuitry 410 and/or RFEMs 515 tocommunicate with the nodes and components of the positioning network.The positioning circuitry 545 may also provide position data and/or timedata to the application circuitry 505, which may use the data tosynchronize operations with various infrastructure (e.g., radio basestations), for turn-by-turn navigation applications, or the like.

In some implementations, the interface circuitry may connect theplatform 500 with Near-Field Communication (NFC) circuitry 540. NFCcircuitry 540 is configured to provide contactless, short-rangecommunications based on radio frequency identification (RFID) standards,wherein magnetic field induction is used to enable communication betweenNFC circuitry 540 and NFC-enabled devices external to the platform 500(e.g., an “NFC touchpoint”). NFC circuitry 540 comprises an NFCcontroller coupled with an antenna element and a processor coupled withthe NFC controller. The NFC controller may be a chip/IC providing NFCfunctionalities to the NFC circuitry 540 by executing NFC controllerfirmware and an NFC stack. The NFC stack may be executed by theprocessor to control the NFC controller, and the NFC controller firmwaremay be executed by the NFC controller to control the antenna element toemit short-range RF signals. The RF signals may power a passive NFC tag(e.g., a microchip embedded in a sticker or wristband) to transmitstored data to the NFC circuitry 540, or initiate data transfer betweenthe NFC circuitry 540 and another active NFC device (e.g., a smartphoneor an NFC-enabled POS terminal) that is proximate to the platform 500.

In some implementations, the interface circuitry may connect theplatform 500 with communications circuitry 560. Though communicationscircuitry 560 is shown as separate from the RFEM 515, these modules canform a single, combined module. The communication circuitry 560 isconfigured to enable the platform 500 to communicate on the cellularnetwork, as subsequently described in relation to FIG. 7.

The driver circuitry 546 may include software and hardware elements thatoperate to control particular devices that are embedded in the platform500, attached to the platform 500, or otherwise communicatively coupledwith the platform 500. The driver circuitry 546 may include individualdrivers allowing other components of the platform 500 to interact withor control various input/output (I/O) devices that may be presentwithin, or connected to, the platform 500. For example, driver circuitry546 may include a display driver to control and allow access to adisplay device, a touchscreen driver to control and allow access to atouchscreen interface of the platform 500, sensor drivers to obtainsensor readings of sensor circuitry 521 and control and allow access tosensor circuitry 521, EMC drivers to obtain actuator positions of theEMCs 522 and/or control and allow access to the EMCs 522, a cameradriver to control and allow access to an embedded image capture device,audio drivers to control and allow access to one or more audio devices.

The power management integrated circuitry (PMIC) 525 (also referred toas “power management circuitry 525”) may manage power provided tovarious components of the platform 500. In particular, with respect tothe baseband circuitry 510, the PMTC 525 may control power-sourceselection, voltage scaling, battery charging, or DC-to-DC conversion.The PMIC 525 may often be included when the platform 500 is capable ofbeing powered by a battery 530, for example, when the device is includedin a UE 101, 201, 301.

In some embodiments, the PMIC 525 may control, or otherwise be part of,various power saving mechanisms of the platform 500. For example, if theplatform 500 is in an RRC_Connected state, where it is still connectedto the RAN node as it expects to receive traffic shortly, then it mayenter a state known as Discontinuous Reception Mode (DRX) after a periodof inactivity. During this state, the platform 500 may power down forbrief intervals of time and thus save power. If there is no data trafficactivity for an extended period of time, then the platform 500 maytransition off to an RRC_Idle state, where it disconnects from thenetwork and does not perform operations such as channel qualityfeedback, handover, etc. The platform 500 goes into a very low powerstate and it performs paging where again it periodically wakes up tolisten to the network and then powers down again. The platform 500 maynot receive data in this state; in order to receive data, it musttransition back to RRC_Connected state. An additional power saving modemay allow a device to be unavailable to the network for periods longerthan a paging interval (ranging from seconds to a few hours). Duringthis time, the device is totally unreachable to the network and maypower down completely. Any data sent during this time incurs a largedelay and it is assumed the delay is acceptable.

A battery 530 may power the platform 500, although in some examples theplatform 500 may be mounted deployed in a fixed location, and may have apower supply coupled to an electrical grid. The battery 530 may be alithium ion battery, a metal-air battery, such as a zinc-air battery, analuminum-air battery, a lithium-air battery, and the like. In someimplementations, such as in V2X applications, the battery 530 may be atypical lead-acid automotive battery.

In some implementations, the battery 530 may be a “smart battery,” whichincludes or is coupled with a Battery Management System (BMS) or batterymonitoring integrated circuitry. The BMS may be included in the platform500 to track the state of charge (SoCh) of the battery 530. The BMS maybe used to monitor other parameters of the battery 530 to providefailure predictions, such as the state of health (SoH) and the state offunction (SoF) of the battery 530. The BMS may communicate theinformation of the battery 530 to the application circuitry 505 or othercomponents of the platform 500. The BMS may also include ananalog-to-digital (ADC) convertor that allows the application circuitry505 to directly monitor the voltage of the battery 530 or the currentflow from the battery 530. The battery parameters may be used todetermine actions that the platform 500 may perform, such astransmission frequency, network operation, sensing frequency, and thelike.

A power block, or other power supply coupled to an electrical grid maybe coupled with the BMS to charge the battery 530. In some examples, thepower block XS30 may be replaced with a wireless power receiver toobtain the power wirelessly, for example, through a loop antenna in thecomputer platform 500. In these examples, a wireless battery chargingcircuit may be included in the BMS. The specific charging circuitschosen may depend on the size of the battery 530, and thus, the currentrequired. The charging may be performed using the Airfuel standardpromulgated by the Airfuel Alliance, the Qi wireless charging standardpromulgated by the Wireless Power Consortium, or the Rezence chargingstandard promulgated by the Alliance for Wireless Power, among others.

User interface circuitry 550 includes various input/output (I/O) devicespresent within, or connected to, the platform 500, and includes one ormore user interfaces designed to enable user interaction with theplatform 500 and/or peripheral component interfaces designed to enableperipheral component interaction with the platform 500. The userinterface circuitry 550 includes input device circuitry and outputdevice circuitry. Input device circuitry includes any physical orvirtual means for accepting an input including, inter alia, one or morephysical or virtual buttons (e.g., a reset button), a physical keyboard,keypad, mouse, touchpad, touchscreen, microphones, scanner, headset,and/or the like. The output device circuitry includes any physical orvirtual means for showing information or otherwise conveyinginformation, such as sensor readings, actuator position(s), or otherlike information. Output device circuitry may include any number and/orcombinations of audio or visual display, including, inter alia, one ormore simple visual outputs/indicators (e.g., binary status indicators(e,g., light emitting diodes (LEDs)) and multi-character visual outputs,or more complex outputs such as display devices or touchscreens (e.g.,Liquid Chrystal Displays (LCD), LED displays, quantum dot displays,projectors, etc.), with the output of characters, graphics, multimediaobjects, and the like being generated or produced from the operation ofthe platform 500. The output device circuitry may also include speakersor other audio emitting devices, printer(s), and/or the like. In someembodiments, the sensor circuitry 521 may be used as the input devicecircuitry (e.g., an image capture device, motion capture device, or thelike) and one or more EMCs may be used as the output device circuitry(e.g., an actuator to provide haptic feedback or the like). In anotherexample, NFC circuitry comprising an NFC controller coupled with anantenna element and a processing device may be included to readelectronic tags and/or connect with another NFC-enabled device.Peripheral component interfaces may include, but are not limited to, anon-volatile memory port, a USB port, an audio jack, a power supplyinterface, etc.

Although not shown, the components of platform 500 may communicate withone another using a suitable bus or interconnect (IX) technology, whichmay include any number of technologies, including ISA, EISA, PCI, PCIx,PCIe, a Time-Trigger Protocol (TTP) system, a FlexRay system, or anynumber of other technologies. The bus/IX may be a proprietary bus/IX,for example, used in a SoC based system. Other bus/IX systems may beincluded, such as an I2C interface, an SPI interface, point-to-pointinterfaces, and a power bus, among others.

FIG. 6 illustrates example components of baseband circuitry 610 andradio front end modules (RFEM) 615 in accordance with variousembodiments. The baseband circuitry 610 corresponds to the base:bandcircuitry 410 and 510 of FIGS. 4 and 5, respectively. The RFEM 615corresponds to the RFEM 415 and 515 of FIGS. 4 and 5, respectively. Asshown, the RFEMs 615 may include Radio Frequency (RF) circuitry 606,front-end module (FEM) circuitry 608, antenna array 611 coupled togetherat least as shown.

The baseband circuitry 610 includes circuitry and/or control logicconfigured to carry out various radio/network protocol and radio controlfunctions that enable communication with one or more radio networks viathe RF circuitry 606. The radio control functions may include, but arenot limited to, signal modulation/demodulation, encoding/decoding, radiofrequency shifting, etc. In some embodiments, modulation/demodulationcircuitry of the baseband circuitry 610 may include Fast-FourierTransform (FFT), preceding, or constellation mapping/demappingfunctionality. In some embodiments, encoding/decoding, circuitry of thebaseband circuitry 610 may include convolution, tail-biting convolution,turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoderfunctionality. Embodiments of modulation/demodulation andencoder/decoder functionality are not limited to these examples and mayinclude other suitable functionality in other embodiments. The basebandcircuitry 610 is configured to process baseband signals received from areceive signal path of the RF circuitry 606 and to generate basebandsignals for a transmit signal path of the RF circuitry 606. The basebandcircuitry 610 is configured to interface with application circuitry405/505 (see FIGS. 4 and 5) for generation and processing of thebaseband signals and for controlling operations of the RF circuitry 606.The baseband circuitry 610 may handle various radio control functions.

The aforementioned circuitry and/or control logic of the basebandcircuitry 610 may include one or more single or multi-core processors.For example, the one or more processors may include a 3G basebandprocessor 604A, a 4G/LTE baseband processor 604B, a 5G/NR basebandprocessor 604C, or some other baseband processor(s) 604D for otherexisting generations, generations in development or to be developed inthe future (e.g., sixth generation (6G), etc.). In other embodiments,some or all of the functionality of baseband processors 604A-D may beincluded in modules stored in the memory 604G and executed via a CentralProcessing Unit (CPU) 604E. In other embodiments, some or all of thefunctionality of baseband processors 604A-D may be provided as hardwareaccelerators (e.g., FPGAs, ASICs, etc.) loaded with the appropriate bitstreams or logic blocks stored in respective memory cells. In variousembodiments, the memory 604G may store program code of a real-time OS(RTOS), which when executed by the CPU 604E (or other basebandprocessor), is to cause the CPU 604E (or other baseband processor) tomanage resources of the baseband circuitry 610, schedule tasks, etc.Examples of the RTOS may include Operating System Embedded (OSE)™provided by Enea®, Nucleus RTOS™ provided by Mentor Graphics®, VersatileReal-Time Executive (VRTX) provided by Mentor Graphics®, ThreadX™provided by Express Logic®, FreeRTOS, RFX OS provided by Qualcomm®, OKL4provided by Open Kernel (OK) Labs®, or any other suitable RTOS, such asthose discussed in this document. In addition, the baseband circuitry610 includes one or more audio digital signal processor(s) (DSP) 604F.The audio DSP(s) 604F include elements for compression/decompression andecho cancellation and may include other suitable processing elements inother embodiments.

In some embodiments, each of the processors 604A-604E include respectivememory interfaces to send/receive data to/from the memory 604G. Thebaseband circuitry 610 may further include one or more interfaces tocommunicatively couple to other circuitries/devices, such as aninterface to send/receive data to/from memory external to the basebandcircuitry 610; an application circuitry interface to send/receive datato/from the application circuitry 405/505 of FIG. 4-XT); an RF circuitryinterface to send/receive data to/from RF circuitry 606 of FIG. 6; awireless hardware connectivity interface to send/receive data to/fromone or more wireless hardware elements (e.g., Near Field Communication(NFC) components, Bluetooth®/Bluetooth® Low Energy components, Wi-Fi®components, and/or the like); and a power management interface tosend/receive power or control signals to/from the PMIC 525.

In alternate embodiments (which may be combined with the above describedembodiments), baseband circuitry 610 comprises one or more digitalbaseband systems, which are coupled with one another via an interconnectsubsystem and to a CPU subsystem, an audio subsystem, and an interfacesubsystem. The digital baseband subsystems may also be coupled to adigital baseband interface and a mixed-signal baseband subsystem viaanother interconnect subsystem. Each of the interconnect subsystems mayinclude a bus system, point-to-point connections, network-on-chip (NOC)structures, and/or some other suitable bus or interconnect technology,such as those discussed in this document. The audio subsystem mayinclude DSP circuitry, buffer memory, program memory, speech processingaccelerator circuitry, data converter circuitry such asanalog-to-digital and digital-to-analog converter circuitry, analogcircuitry including one or more of amplifiers and filters, and/or otherlike components. In an aspect of the present disclosure, basebandcircuitry 610 may include protocol processing circuitry with one or moreinstances of control circuitry (not shown) to provide control functionsfor the digital baseband circuitry and/or radio frequency circuitry(e.g., the radio front end modules 615).

Although not shown by FIG. 6, in some embodiments, the basebandcircuitry 610 includes individual processing device(s) to operate one ormore wireless communication protocols (e.g., a “multi-protocol basebandprocessor” or “protocol processing circuitry”) and individual processingdevice(s) to implement PHY layer functions. In these embodiments, thePHY layer functions include the aforementioned radio control functions.In these embodiments, the protocol processing circuitry operates orimplements various protocol layers/entities of one or more wirelesscommunication protocols. In a first example, the protocol processingcircuitry may operate LTE protocol entities and/or 5G/NR protocolentities when the baseband circuitry 610 and/or RF circuitry 606 arepart of mmWave communication circuitry or some other suitable cellularcommunication circuitry. In the first example, the protocol processingcircuitry would operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. Ina second example, the protocol processing circuitry may operate one ormore IEEE-based protocols when the baseband circuitry 610 and/or RFcircuitry 606 are part of a Wi-Fi communication system. In the secondexample, the protocol processing circuitry would operate Wi-Fi MAC andlogical link control (LLC) functions, The protocol processing circuitrymay include one or more memory structures (e.g., 604G) to store programcode and data for operating the protocol functions, as well as one ormore processing cores to execute the program code and perform variousoperations using the data. The baseband circuitry 610 may also supportradio communications for more than one wireless protocol.

The various hardware elements of the baseband circuitry 610 discussed inthis document may be implemented, for example, as a solder-downsubstrate including one or more integrated circuits (ICs), a singlepackaged IC soldered to a main circuit board or a multi-chip modulecontaining two or more ICs. In one example, the components of thebaseband circuitry 610 may be suitably combined in a single chip orchipset, or disposed on a same circuit board. In another example, someor all of the constituent components of the baseband circuitry 610 andRF circuitry 606 may be implemented together such as, for example, asystem on a chip (SoC) or System-in-Package (SiP). In another example,some or all of the constituent components of the baseband circuitry 610may be implemented as a separate SoC that is communicatively coupledwith and RF circuitry 606 (or multiple instances of RF circuitry 606).In yet another example, some or all of the constituent components of thebaseband circuitry 610 and the application circuitry 405/505 may beimplemented together as individual SoCs mounted to a same circuit board(e.g., a “multi-chip package”).

In some embodiments, the baseband circuitry 610 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, the baseband circuitry 610 may supportcommunication with an E-UTRAN or other WMAN, a WLAN, a WPAN. Embodimentsin which the baseband circuitry 610 is configured to support radiocommunications of more than one wireless protocol may be referred to asmulti-mode baseband circuitry.

RF circuitry 606 enables communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 606 may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. RF circuitry 606 may include a receive signal path, which mayinclude circuitry to down-convert RF signals received from the FEMcircuitry 608 and provide baseband signals to the baseband circuitry610. RF circuitry 606 may also include a transmit signal path, which mayinclude circuitry to up-convert baseband signals provided by thebaseband circuitry 610 and provide RF output signals to the FEMcircuitry 608 for transmission.

In some embodiments, the receive signal path of the RF circuitry 606includes mixer circuitry 606 a, amplifier circuitry 606 b and filtercircuitry 606 c. In some embodiments, the transmit signal path of the RFcircuitry 606 may include filter circuitry 606 c and mixer circuitry 606a. RF circuitry 606 may also include synthesizer circuitry 606 d forsynthesizing a frequency for use by the mixer circuitry 606 a of thereceive signal path and the transmit signal path. In some embodiments,the mixer circuitry 606 a of the receive signal path may be configuredto down-convert RF signals received from the FEM circuitry 608 based onthe synthesized frequency provided by synthesizer circuitry 606 d. Theamplifier circuitry 606 b may be configured to amplify thedown-converted signals and the filter circuitry 606 c may be a low-passfilter (LPF) or band-pass filter (BPF) configured to remove unwantedsignals from the down-converted signals to generate output basebandsignals. Output baseband signals may be provided to the basebandcircuitry 610 for further processing. In some embodiments, the outputbaseband signals may be zero-frequency baseband signals, although thisis not a requirement. In some embodiments, mixer circuitry 606 a of thereceive signal path may comprise passive mixers, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 606 a of the transmit signalpath may be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 606 d togenerate RF output signals for the FEM circuitry 608. The basebandsignals may be provided by the baseband circuitry 610 and may befiltered by filter circuitry 606 c.

In some embodiments, the mixer circuitry 606 a of the receive signalpath and the mixer circuitry 606 a of the transmit signal path mayinclude two or more mixers and may be arranged for quadraturedownconversion and upconversion, respectively. In some embodiments, themixer circuitry 606 a of the receive signal path and the mixer circuitry606 a of the transmit signal path may include two or more mixers and maybe arranged for image rejection (e.g., Hartley image rejection). In someembodiments, the mixer circuitry 606 a of the receive signal path andthe mixer circuitry 606 a of the transmit signal path may be arrangedfor direct downconversion and direct upconversion, respectively. In someembodiments, the mixer circuitry 606 a of the receive signal path andthe mixer circuitry 606 a of the transmit signal path may be configuredfor super-heterodyne operation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, the RFcircuitry 606 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry and the baseband circuitry610 may include a digital baseband interface to communicate with the RFcircuitry 606.

In some dual-mode embodiments, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 606 d may be afractional-N synthesizer or a fractional N/N+1 synthesizer, although thescope of the embodiments is not limited in this respect as other typesof frequency synthesizers may be suitable. For example, synthesizercircuitry 606 d may be a delta-sigma synthesizer, a frequencymultiplier, or a synthesizer comprising a phase-locked loop with afrequency divider.

The synthesizer circuitry 606 d may be configured to synthesize anoutput frequency for use by the mixer circuitry 606 a of the RFcircuitry 606 based on a frequency input and a divider control input. Insome embodiments, the synthesizer circuitry 606 d may be a fractionalN/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 610 orthe application circuitry 405/505 depending on the desired outputfrequency. In some embodiments, a divider control input (e.g., N) may bedetermined from a look-up table based on a channel indicated by theapplication circuitry 405/505.

Synthesizer circuitry 606 d of the RF circuitry 606 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some embodiments, the divider may be a dual modulusdivider (DMD) and the phase accumulator may be a digital phaseaccumulator (DPA). In some embodiments, the DMD may be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example embodiments, theDLL may include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump and a D-type flip-flop. In these embodiments,the delay elements may be configured to break a VCO period up into Ndequal packets of phase, where Nd is the number of delay elements in thedelay line. In this way, the DLL provides negative feedback to helpensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 606 d may be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someembodiments, the output frequency may be a LO frequency (fLO). In someembodiments, the RF circuitry 606 may include an IQ/polar converter.

FEM circuitry 608 may include a receive signal path, which may includecircuitry configured to operate on RF signals received from antennaarray 611, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 606 for furtherprocessing. FEM circuitry 608 may also include a transmit signal path,which may include circuitry configured to amplify signals fortransmission provided by the RF circuitry 606 for transmission by one ormore of antenna elements of antenna array 611. In various embodiments,the amplification through transmit or receive signal paths may be donesolely in the RF circuitry 606, solely in the FEM circuitry 608, or inboth the RF circuitry 606 and the FEM circuitry 608.

In some embodiments, the FEM circuitry 608 may include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry 608 may include a receive signal path and a transmit signalpath. The receive signal path of the EM circuitry 608 may include an LNAto amplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 606). The transmitsignal path of the FEM circuitry 608 may include a power amplifier (PA)to amplify input RF signals (e.g., provided by RF circuitry 606), andone or more filters to generate RF signals for subsequent transmissionby one or more antenna elements of the antenna array 611.

The antenna array 611 comprises one or more antenna elements, each ofwhich is configured convert electrical signals into radio waves totravel through the air and to convert received radio waves intoelectrical signals. For example, digital baseband signals provided bythe baseband circuitry 610 is converted into analog RF signals (e.g.,modulated waveform) that will be amplified and transmitted via theantenna elements of the antenna array 611 including one or more antennaelements (not shown). The antenna elements may be omnidirectional,direction, or a combination thereof. The antenna elements may be formedin a multitude of arranges as are known and/or discussed in thisdocument. The antenna array 611 may comprise microstrip antennas orprinted antennas that are fabricated on the surface of one or moreprinted circuit boards. The antenna array 611 may be formed in as apatch of metal foil (e.g., a patch antenna) in a variety of shapes, andmay be coupled with the RF circuitry 606 and/or FEM circuitry 608 usingmetal transmission lines or the like.

Processors of the application circuitry 405/505 and processors of thebaseband circuitry 610 may be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 610, alone or in combination, may be used execute Layer 3,Layer 2, or Layer 1 functionality, while processors of the applicationcircuitry 405/505 may utilize data (e.g., packet data) received fromthese layers and further execute Layer 4 functionality (e.g., TCP andUDP layers). As referred to in this document, Layer 3 may comprise a RRClayer, described in further detail below. As referred to in thisdocument, Layer 2 may comprise a MAC layer, an RLC layer, and a PDCPlayer, described in further detail below. As referred to in thisdocument, Layer 1 may comprise a PHY layer of a UE/RAN node, describedin further detail below.

FIG. 7 illustrates an example block diagram of cellular communicationcircuitry 560. It is noted that the block diagram of the cellularcommunication circuitry 560 of FIG. 7 is an example of a cellularcommunication circuit, but that other configurations are also possible.In some implementations, the cellular communication circuitry 560 may beincluded in a communication device, such as the platform 500 describedabove. As noted above, platform 500 may be a UE device, a mobile deviceor mobile station, a wireless device or wireless station, a desktopcomputer or computing device, a mobile computing device (e.g., a laptop,notebook, or portable computing device), a tablet, a wireless sensor,surveillance equipment, or wearables devices, or a combination of them,among other devices.

The cellular communication circuitry 560 may couple (e.g.,communicatively, directly, or indirectly) to one or more antennas, suchas antennas of antenna array 611 as shown (e.g., in FIG. 6). In someimplementations, the cellular communication circuitry 560 includes or iscommunicatively coupled to dedicated receive chains, processors, orradios for multiple RATs (e.g., a first receive chain for LTE and asecond receive chain for 5G NR). For example, as shown in FIG. 7,cellular communication circuitry 560 may include a modem 710 and a modem720. Modem 710 may be configured for communications according to a firstRAT, e.g., such as LTE or LTE-A, and modem 720 may be configured forcommunications according to a second RAT, e.g., such as 5G NR.

The modem 710 includes one or more processors 712 and a memory 716 incommunication with the processors 712. The modem 710 is in communicationwith a radio frequency front end module 515 a (e.g., RFEM 515). The RFEM515 a may include circuitry for transmitting and receiving radiosignals. For example, the RF front end 730 includes receive circuitry(RX) 732 and transmit circuitry (TX) 734. In some implementations, thereceive circuitry 732 is in communication with downlink (DL) front end750, which may include circuitry for receiving radio signals via antenna611 a.

Similarly, the modem 720 includes one or more processors 722 and amemory 726 in communication with the processors 722. The modem 720 is incommunication with an RFEM 515 b. The RFEM 515 b may include circuitryfor transmitting and receiving radio signals. For example, the RF frontend 740 may include receive circuitry 742 and transmit circuitry 744. Insome implementations, the receive circuitry 742 is in communication withDL front end 760, which may include circuitry for receiving radiosignals via antenna 611 b.

The modem 710 may include hardware and software components forimplementing the above features or for time division multiplexing ULdata for NSA NR operations, as well as the various other techniquesdescribed in this document. The processors 712 may be configured toimplement part or all of the features described in this document, e.g.,by executing program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively (or inaddition), the processor 712 may be configured as a programmablehardware element, such as an FPGA (Field Programmable Gate Array), or asan ASIC (Application Specific Integrated Circuit). Alternatively (or inaddition) the processor 712, in conjunction with one or more of theother components 730, 732, 734, 750, 770, 772, and 611 may be configuredto implement some or all of the features described in this document.

The processors 712 may include one or more processing elements. Thus,processors 712 may include one or more integrated circuits (ICs) thatare configured to perform the functions of processors 712. In addition,each integrated circuit may include circuitry (e.g., first circuitry,second circuitry, etc.) configured to perform the functions ofprocessors 712.

The modem 720 may include hardware and software components forimplementing the above features for time division multiplexing UL datafor NSA NR operations, as well as the various other techniques describedin this document. The processors 722 may be configured to implement partor all of the features described in this document, e.g., by executingprogram instructions stored on a memory medium (e.g., a non-transitorycomputer-readable memory medium). Alternatively (or in addition),processor 722 may be configured as a programmable hardware element, suchas an FPGA (Field Programmable Gate Array), or as an ASIC (ApplicationSpecific Integrated Circuit). Alternatively (or in addition) theprocessor 722, in conjunction with one or more of the other components740, 742, 744, 750, 770, 772, and 611 may be configured to implementpart or all of the features described in this document.

In addition, the processors 722 may include one or more processingelements. Thus, the processors 722 may include one or more integratedcircuits (ICs) that are configured to perform the functions ofprocessors 722. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processors 722.

FIG. 8 is a block diagram illustrating example protocol functions forimplementing in a wireless communication device according to variousembodiments. In particular, FIG. 8 includes an arrangement 800 showinginterconnections between various protocol layers/entities. The followingdescription of FIG. 8 is provided for various protocol layers/entitiesthat operate in conjunction with the 5G/NR system standards and LTEsystem standards, but some or all of the aspects of FIG. 8 may beapplicable to other wireless communication network systems as well.

The protocol layers of arrangement 800 may include one or more of PHY810, MAC 820, RLC 830, PDCP 840, SDAP 847, RRC 855, and NAS layer 857,in addition to other higher layer functions not illustrated. Theprotocol layers may include one or more service access points (e.g.,items 859, 856, 850, 849, 845, 835, 825, and 815 in FIG. 8) that mayprovide communication between two or more protocol layers.

The PHY 810 may transmit and receive physical layer signals 805 that maybe received from or transmitted to one or more other communicationdevices. The physical layer signals 805 may comprise one or morephysical channels, such as those discussed in this document. The PHY 810may further perform link adaptation or adaptive modulation and coding(AMC), power control, cell search (e.g., for initial synchronization andhandover purposes), and other measurements used by higher layers, suchas the RRC 855. The THY 810 may still further perform error detection onthe transport channels, forward error correction (FEC) coding/decodingof the transport channels, modulation/demodulation of physical channels,interleaving, rate matching, mapping onto physical channels, and MIMOantenna processing. In embodiments, an instance of PHY 810 may processrequests from and provide indications to an instance of MAC 820 via oneor more PHY-SAP 815. According to some embodiments, requests andindications communicated via PHY-SAP 815 may comprise one or moretransport channels.

Instance(s) of MAC 820 may process requests from, and provideindications to, an instance of RLC 830 via one or more MAC-SAPs 825.These requests and indications communicated via the MAC-SAP 825 maycomprise one or more logical channels. The MAC 820 may perform mappingbetween the logical channels and transport channels, multiplexing of MACSDUs from one or more logical channels onto TBs to be delivered to PRY810 via the transport channels, de-multiplexing MAC SDUs to one or morelogical channels from TBs delivered from the PHY 810 via transportchannels, multiplexing MAC SDUs onto TBs, scheduling informationreporting, error correction through HARQ, and logical channelprioritization.

Instance(s) of RLC 830 may process requests from and provide indicationsto an instance of PDCP 840 via one or more radio link control serviceaccess points (RLC-SAP) 835. These requests and indications communicatedvia RLC-SAP 835 may comprise one or more RLC channels. The RLC 830 mayoperate in a plurality of modes of operation, including: TransparentMode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC830 may execute transfer of upper layer protocol data units (PDUs),error correction through automatic repeat request (ARQ) for AM datatransfers, and concatenation, segmentation and reassembly of RLC SDUsfor UM and AM data transfers. The RLC 830 may also executere-segmentation of RLC data PDUs for AM data transfers, reorder RLC dataPDUs for UM and AM data transfers, detect duplicate data for UM and AMdata transfers, discard RLC SDUs for UM and AM data transfers, detectprotocol errors for AM data transfers, and perform RLC re-establishment.

Instance(s) of PDCP 840 may process requests from and provideindications to instance(s) of RRC 855 and/or instance(s) of SDAP 847 viaone or more packet data convergence protocol service access points(PDCP-SAP) 845. These requests and indications communicated via PDCP-SAP845 may comprise one or more radio bearers. The PDCP 840 may executeheader compression and decompression of IP data, maintain PDCP SequenceNumbers (SNs), perform in-sequence delivery of upper layer PDUs atre-establishment of lower layers, eliminate duplicates of lower layerSDUs at re-establishment of lower layers for radio bearers mapped on RLCAM, cipher and decipher control plane data, perform integrity protectionand integrity verification of control plane data, control timer-baseddiscard of data, and perform security operations (e.g., ciphering,deciphering, integrity protection, integrity verification, etc.).

Instance(s) of SDAP 847 may process requests from and provideindications to one or more higher layer protocol entities via one ormore SDAP-SAP 849. These requests and indications communicated viaSDAP-SAP 849 may comprise one or more QoS flows. The SDAP 847 may mapQoS flows to DRBs, and vice versa, and may also mark QFIs in DL and ULpackets. A single SDAP entity 847 may be configured for an individualPDU session. In the UL direction, the NG-RAN 110 may control the mappingof QoS Flows to DRB(s) in two different ways, reflective mapping orexplicit mapping. For reflective mapping, the SDAP 847 of a UE 101 maymonitor the QFIs of the DL packets for each DRB, and may apply the samemapping for packets flowing in the UL direction. For a DRB, the SDAP 847of the UE 101 may map the UL packets belonging to the QoS flows(s)corresponding to the QoS flow ID(s) and PDU session observed in the DLpackets for that DRB. To enable reflective mapping, the NG-RAN 310 maymark DL packets over the interface with a QoS flow ID. The explicitmapping may involve the RRC 855 configuring the SDAP 847 with anexplicit QoS flow to DRB mapping rule, which may be stored and followedby the SDAP 847. In embodiments, the SDAP 847 may only be used in NRimplementations and may not be used in LTE implementations.

The RRC 855 may configure, via one or more management service accesspoints (M-SAP), aspects of one or more protocol layers, which mayinclude one or more instances of PHY 810, MAC 820, RLC 830, PDCP 840 andSDAP 847. In embodiments, an instance of RRC 855 may process requestsfrom and provide indications to one or more NAS entities 857 via one ormore RRC-SAPS 856. The main services and functions of the RRC 855 mayinclude broadcast of system information (e.g., included in MIBs or SIBsrelated to the NAS), broadcast of system information related to theaccess stratum (AS), paging, establishment, maintenance and release ofan RRC connection between the UE 101 and RAN 110 (e.g., RRC connectionpaging, RRC connection establishment, RRC connection modification, andRRC connection release), establishment, configuration, maintenance andrelease of point to point Radio Bearers, security functions includingkey management, inter-RAT mobility, and measurement configuration for UEmeasurement reporting. The MIBs and SIBs may comprise one or more IEs,which may each comprise individual data fields or data structures.

The NAS 857 may form the highest stratum of the control plane betweenthe UE 101 and the AMF 321. The NAS 857 may support the mobility of theUEs 101 and the session management procedures to establish and maintainIP connectivity between the UE 101 and a P-GW in LTE systems.

According to various embodiments, one or more protocol entities ofarrangement 800 may be implemented in UEs 101, RAN nodes 111, AMF 321 inNR implementations or MME 221 in LTE implementations, UPF 302 in NRimplementations or S-GW 222 and P-GW 223 in LTE implementations, or thelike to be used for control plane or user plane communications protocolstack between the aforementioned devices. In such embodiments, one ormore protocol entities that may be implemented in one or more of UE 101,gNB 111, AMF 321, etc. may communicate with a respective peer protocolentity that may be implemented in or on another device using theservices of respective lower layer protocol entities to perform suchcommunication. In some embodiments, a gNB-CU of the gNB 111 may host theRRC 855, SDAP 847, and PDCP 840 of the gNB that controls the operationof one or more gNB-DUs, and the gNB-DUs of the gNB 111 may each host theRLC 830, MAC 820, and PITY 810 of the gNB 111.

In a first example, a control plane protocol stack may comprise, inorder from highest layer to lowest layer, NAS 857, RRC 855, PDCP 840,RLC 830, MAC 820, and PHY 810. In this example, upper layers 860 may bebuilt on top of the NAS 857, which includes an IP layer 861, an SCTP862, and an application layer signaling protocol (AP) 863.

In NR implementations, the AP 863 may be an NG application protocollayer (NGAP or NG-AP) 863 for the NG interface 113 defined between theNG-RAN node 111 and the AMF 321, or the AP 863 may be an Xn applicationprotocol layer (XnAP or Xn-AP) 863 for the Xn interface 112 that isdefined between two or more RAN nodes 111.

The NG-AP 863 may support the functions of the NG interface 113 and maycomprise Elementary Procedures (EPs). An NG-AP EP may be a unit ofinteraction between the NG-RAN node 111 and the AMF 321. The NG-AP 863services may comprise two groups: UE-associated services (e.g., servicesrelated to a UE 101) and non-UE-associated services (e.g., servicesrelated to the whole NG interface instance between the NG-RAN node 111and AMF 321). These services may include functions including, but notlimited to: a paging function for the sending of paging requests toNG-RAN nodes 111 involved in a particular paging area; a UE contextmanagement function for allowing the AMF 321 to establish, modify,and/or release a UE context in the AMF 321 and the NG-RAN node 111; amobility function for UEs 101 in ECM-CONNECTED mode for intra-system HOsto support mobility within NG-RAN and inter-system HOs to supportmobility from/to EPS systems; a NAS Signaling Transport function fortransporting or rerouting NAS messages between UE 101 and AMF 321; a NASnode selection function for determining an association between the AMF321 and the UE 101; NG interface management function(s) for setting upthe NG interface and monitoring for errors over the NG interface; awarning message transmission function for providing means to transferwarning messages via NG interface or cancel ongoing broadcast of warningmessages; a Configuration Transfer function for requesting andtransferring of RAN configuration information (e.g., SON information,performance measurement (PM) data, etc.) between two RAN nodes 111 viaCN 120; and/or other like functions.

The XnAP 863 may support the functions of the Xn interface 112 and maycomprise XnAP basic mobility procedures and XnAP global procedures. TheXnAP basic mobility procedures may comprise procedures used to handle UEmobility within the NG RAN 111 (or E-UTRAN 210), such as handoverpreparation and cancellation procedures, SN Status Transfer procedures,UE context retrieval and UE context release procedures, RAN pagingprocedures, dual connectivity related procedures, and the like. The XnAPglobal procedures may comprise procedures that are not related to aspecific UE 101, such as Xn interface setup and reset procedures, NG-RANupdate procedures, cell activation procedures, and the like.

In LTE implementations, the AP 863 may be an S1 Application Protocollayer (S1-AP) 863 for the S1 interface 113 defined between an E-UTRANnode 111 and an MME, or the AP 863 may be an X2 application protocollayer (X2AP or X2-AP) 863 for the X2 interface 112 that is definedbetween two or more E-UTRAN nodes 111.

The S1 Application Protocol layer (S1-AP) 863 may support the functionsof the S1 interface, and similar to the NG-AP discussed previously, theS1-AP may comprise S1-AP EPs. An S1-AP EP may be a unit of interactionbetween the E-UTRAN node 111 and an MME 221 within an LTE CN 120. TheS1-AP 863 services may comprise two groups: UE-associated services andnon UE-associated services. These services perform functions including,but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UEcapability indication, mobility, NAS signaling transport, RANInformation Management (RIM), and configuration transfer.

The X2AP 863 may support the functions of the X2 interface 112 and maycomprise X2AP basic mobility procedures and X2AP global procedures. TheX2AP basic mobility procedures may comprise procedures used to handle UEmobility within the E-UTRAN 120, such as handover preparation andcancellation procedures, SN Status Transfer procedures, UE contextretrieval and UE context release procedures, RAN paging procedures, dualconnectivity related procedures, and the like. The X2AP globalprocedures may comprise procedures that are not related to a specificLIE 101, such as X2 interface setup and reset procedures, loadindication procedures, error indication procedures, cell activationprocedures, and the like.

The SCTP layer (alternatively referred to as the SCTP/IP layer) 862 mayprovide guaranteed delivery of application layer messages (e.g., NGAP orXnAP messages in NR implementations, or S1-AP or X2AP messages in LTEimplementations). The SCTP 862 may ensure reliable delivery of signalingmessages between the RAN node 111 and the AMF 321/MME 221 based, inpart, on the IP protocol, supported by the IP 861. The Internet Protocollayer (IP) 861 may be used to perform packet addressing and routingfunctionality. In some implementations the IP layer 861 may usepoint-to-point transmission to deliver and convey PDUs. In this regard,the RAN node 111 may comprise L2 and L1 layer communication links (e.g.,wired or wireless) with the MME/AMF to exchange information.

In a second example, a user plane protocol stack may comprise, in orderfrom highest layer to lowest layer, SDAP 847, PDCP 840, RLC 830, MAC820, and PHY 810. The user plane protocol stack may be used forcommunication between the UE 101, the RAN node 111, and UPF 302 in NRimplementations or an S-GW 222 and P-GW 223 in LTE implementations. Inthis example, upper layers 851 may be built on top of the SDAP 847, andmay include a user datagram protocol (UDP) and IP security layer(UDP/IP) 852, a General Packet Radio Service (GPRS) Tunneling Protocolfor the user plane layer (GTP-U) 853, and a User Plane PDU layer (UPPDU) 863.

The transport network layer 854 (also referred to as a “transportlayer”) may be built on IP transport, and the GTP-U 853 may be used ontop of the UDP/IP layer 852 (comprising a UDP layer and IP layer) tocarry user plane PDUs (UP-PDUs). The IP layer (also referred to as the“Internet layer”) may be used to perform packet addressing and routingfunctionality. The IP layer may assign IP addresses to user data packetsin any of IPv4, IPv6, or PPP formats, for example.

The GTP-U 853 may be used for carrying user data within the GPRS corenetwork and between the radio access network and the core network. Theuser data transported can be packets in any of IPv4, IPv6, or PPPformats, for example. The UDP/IP 852 may provide checksums for dataintegrity, port numbers for addressing different functions at the sourceand destination, and encryption and authentication on the selected dataflows. The RAN node 111 and the S-GW 222 may utilize an S1-U interfaceto exchange user plane data via a protocol stack comprising an L1 layer(e.g., PHY 810), an L2 layer (e.g., MAC 820, RLC 830, PDCP 840, and/orSDAP 847), the UDP/IP layer 852, and the GTP-U 853. The S-GW 222 and theP-GW 223 may utilize an S5/S8a interface to exchange user plane data viaa protocol stack comprising an L1 layer, an L2 layer, the UDP/IP layer852, and the GTP-U 853. As discussed previously, NAS protocols maysupport the mobility of the UE 101 and the session management proceduresto establish and maintain IP connectivity between the UE 101 and theP-GW 223.

Moreover, although not shown by FIG. 8, an application layer may bepresent above the AP 863 and/or the transport network layer 854. Theapplication layer may be a layer in which a user of the UE 101, RAN node111, or other network element interacts with software applications beingexecuted, for example, by application circuitry 405 or applicationcircuitry 505, respectively. The application layer may also provide oneor more interfaces for software applications to interact withcommunications systems of the UE 101 or RAN node 111, such as thebaseband circuitry 610. In some implementations the IP layer and/or theapplication layer may provide the same or similar functionality aslayers 5-7, or portions thereof, of the Open Systems Interconnection(OSI) model (e.g., OSI Layer 7—the application layer, OSI Layer 6—thepresentation layer, and OSI Layer 5—the session layer).

FIG. 9 illustrates components of a core network in accordance withvarious embodiments. The components of the CN 220 may be implemented inone physical node or separate physical nodes including components toread and execute instructions from a machine-readable orcomputer-readable medium (e.g., a non-transitory machine-readablestorage medium). In embodiments, the components of CN 320 may beimplemented in a same or similar manner as discussed in this documentwith regard to the components of CN 220. In some embodiments, NFV isutilized to virtualize any or all of the above-described network nodefunctions via executable instructions stored in one or morecomputer-readable storage mediums (described in further detail below). Alogical instantiation of the CN 220 may be referred to as a networkslice 901, and individual logical instantiations of the CN 220 mayprovide specific network capabilities and network characteristics. Alogical instantiation of a portion of the CN 220 may be referred to as anetwork sub-slice 902 (e.g., the network sub-slice 902 is shown toinclude the P-GW 223 and the PCRF 226).

As used in this document, the terms “instantiate,” “instantiation,” andthe like may refer to the creation of an instance, and an “instance” mayrefer to a concrete occurrence of an object, which may occur, forexample, during execution of program code. A network instance may referto information identifying a domain, which may be used for trafficdetection and routing in case of different IP domains or overlapping IPaddresses. A network slice instance may refer to a set of networkfunctions (NFs) instances and the resources (e.g., compute, storage, andnetworking resources) required to deploy the network slice.

With respect to 5G systems (see, e.g., FIG. 3), a network slice alwayscomprises a RAN part and a CN part. The support of network slicingrelies on the principle that traffic for different slices is handled bydifferent PDU sessions. The network can realize the different networkslices by scheduling and also by providing different L1/L2configurations. The UE 301 provides assistance information for networkslice selection in an appropriate RRC message, if it has been providedby NAS. While the network can support large number of slices, the UEneed not support more than 8 slices simultaneously.

A network slice may include the CN 320 control plane and user plane NFs,NG-RANs 310 in a serving PLMN, and a N3IWF functions in the servingPLMN. Individual network slices may have different S-NSSAI and/or mayhave different SSTs. NSSAI includes one or more S-NSSAIs, and eachnetwork slice is uniquely identified by an S-NSSAI. Network slices maydiffer for supported features and network functions optimizations,and/or multiple network slice instances may deliver the sameservice/features but for different groups of UEs 301 (e.g., enterpriseusers). For example, individual network slices may deliver differentcommitted service(s) and/or may be dedicated to a particular customer orenterprise. In this example, each network slice may have differentS-NSSAIs with the same SST but with different slice differentiators.Additionally, a single UE may be served with one or more network sliceinstances simultaneously via a 5G AN and associated with eight differentS-NSSAIs. Moreover, an AMF 321 instance serving an individual UE 301 maybelong to each of the network slice instances serving that UE.

Network Slicing in the NG-RAN 310 involves RAN slice awareness. RANslice awareness includes differentiated handling of traffic fordifferent network slices, which have been pre-configured. Sliceawareness in the NG-RAN 310 is introduced at the PDU session level byindicating the S-NSSAI corresponding to a PDU session in all signalingthat includes PDU session resource information. How the NG-RAN 310supports the slice enabling in terms of NG-RAN functions (e.g., the setof network functions that comprise each slicer is implementationdependent. The NG-RAN 310 selects the RAN part of the network sliceusing assistance information provided by the UE 301 or the 5GS 320,which unambiguously identifies one or more of the pre-configured networkslices in the PLMN. The NG-RAN 310 also supports resource management andpolicy enforcement between slices as per SLAs. A single NG-RAN node maysupport multiple slices, and the NG-RAN 310 may also apply anappropriate RRM policy for the SLA in place to each supported slice. TheNG-RAN 310 may also support QoS differentiation within a slice.

The NG-RAN 310 may also use the UE assistance information for theselection of an AMF 321 during an initial attach, if available. TheNG-RAN 310 uses the assistance information for routing the initial NASto an AMF 321. If the NG-RAN 310 is unable to select an AMF 321 usingthe assistance information, or the UE 301 does not provide any suchinformation, the NG-RAN 310 sends the NAS signaling to a default AMF321, which may be among a pool of ANFs 321. For subsequent accesses, theUE 301 provides a temp ID, which is assigned to the UE 301 by the 5GC320, to enable the NG-RAN 310 to route the NAS message to theappropriate AMF 321 as long as the temp ID is valid. The NG-RAN 310 isaware of, and can reach, the AMF 321 that is associated with the tempID. Otherwise, the method for initial attach applies.

The NG-RAN 310 supports resource isolation between slices. NG-RAN 310resource isolation may be achieved by means of RRM policies andprotection mechanisms that should avoid that shortage of sharedresources if one slice breaks the service level agreement for anotherslice. in some implementations, it is possible to fully dedicate NG-RAN310 resources to a certain slice. How NG-RAN 310 supports resourceisolation is implementation dependent.

Some slices may be available only in part of the network. Awareness inthe NG-RAN 310 of the slices supported in the cells of its neighbors maybe beneficial for inter-frequency mobility in connected mode. The sliceavailability may not change within the UE's registration area. TheNG-RAN 310 and the 5GC 320 are responsible to handle a service requestfor a slice that may or may not be available in a given area. Admissionor rejection of access to a slice may depend on factors such as supportfor the slice, availability of resources, support of the requestedservice by NG-RAN 310.

The UE 301 may be associated with multiple network slicessimultaneously. In case the UE 301 is associated with multiple slicessimultaneously, only one signaling connection is maintained, and forintra-frequency cell reselection, the UE 301 tries to camp on the bestcell. For inter-frequency cell reselection, dedicated priorities can beused to control the frequency on which the UE 301 camps. The 5GC 320 isto validate that the UE 301 has the rights to access a network slice.Prior to receiving an Initial Context Setup Request message, the NG-RAN310 may be allowed to apply some provisional/local policies, based onawareness of a particular slice that the UE 301 is requesting to access.During the initial context setup, the NG-RAN 310 is informed of theslice for which resources are being requested.

NFV architectures and infrastructures may be used to virtualize one ormore NFs, alternatively performed by proprietary hardware, onto physicalresources comprising a combination of industry-standard server hardware,storage hardware, or switches. In other words, NFV systems can be usedto execute virtual or reconfigurable implementations of one or more EPCcomponents/functions,

FIG. 10 is a block diagram illustrating components, according to someexample embodiments, of a system 1000 to support NFV. The system 1000 isillustrated as including a VIM 1002, an NFVI 1004, a VNFM 1006, VNFs1008, an EM 1010, an NFVO 1012, and a NM 1014.

The VIM 1002 manages the resources of the NFVI 1004, The NFVI 1004 caninclude physical or virtual resources and applications (includinghypervisors) used to execute the system 1000. The VIM 1002 may managethe life cycle of virtual resources with the NFVI 1004 (e.g., creation,maintenance, and tear down of VMs associated with one or more physicalresources), track VM instances, track performance, fault and security ofVM instances and associated physical resources, and expose VM instancesand associated physical resources to other management systems.

The VNFM 1006 may manage the VNFs 1008. The VNFs 1008 may be used toexecute EPC components/functions. The VNFM 1006 may manage the lifecycle of the VNFs 1008 and track performance, fault and security of thevirtual aspects of VNFs 1008. The EM 1010 may track the performance,fault and security of the functional aspects of VNFs 1008. The trackingdata from the VNFM 1006 and the EM 1010 may comprise, for example, PMdata used by the VIM 1002 or the NFVI 1004. Both the VNFM 1006 and theEM 1010 can scale up/down the quantity of VNFs of the system 1000.

The NFVO 1012 may coordinate, authorize, release and engage resources ofthe NFVI 1004 in order to provide the requested service (e.g., toexecute an EPC function, component, or slice). The NM 1014 may provide apackage of end-user functions with the responsibility for the managementof a network, which may include network elements with VNFs,non-virtualized network functions, or both (management of the VNFs mayoccur via the EM 1010).

FIG. 11 is a block diagram illustrating components, according to someexample embodiments, able to read instructions from a machine-readableor computer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed in this document. Specifically, FIG. 11 shows a diagrammaticrepresentation of hardware resources 1100 including one or moreprocessors (or processor cores) 1110, one or more memory/storage devices1120, and one or more communication resources 1130, each of which may becommunicatively coupled via a bus 1140. For embodiments where nodevirtualization (e.g., NFV) is utilized, a hypervisor 1102 may beexecuted to provide an execution environment for one or more networkslices/sub-slices to utilize the hardware resources 1100.

The processors 1110 may include, for example, a processor 1112 and aprocessor 1114. The processor(s) 1110 may he, for example, a centralprocessing unit (CPU), a reduced instruction set computing (RISC)processor, a complex instruction set computing (CISC) processor, agraphics processing unit (GPU), a DSP such as a baseband processor, anASTC, an FPGA, a radio-frequency integrated circuit (RFIC), anotherprocessor (including those discussed in this document), or any suitablecombination thereof.

The memory/storage devices 1120 may include main memory, disk storage,or any suitable combination thereof. The memory/storage devices 1120 mayinclude, but are not limited to, any type of volatile or nonvolatilememory such as dynamic random access memory (DRAM), static random accessmemory (SRAM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), Flashmemory, solid-state storage, etc.

The communication resources 1130 may include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 1104 or one or more databases 1106 via anetwork 1108. For example, the communication resources 1130 may includewired communication components (e.g., for coupling via USB), cellularcommunication components, NFC components, Bluetooth® (or Bluetooth® LowEnergy) components, Wi-Fi® components, and other communicationcomponents.

Instructions 1150 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 1110 to perform any one or more of the methodologiesdiscussed in this document. The instructions 1150 may reside, completelyor partially, within at least one of the processors 1110 (e.g., withinthe processor's cache memory), the memory/storage devices 1120, or anysuitable combination thereof. Furthermore, any portion of theinstructions 1150 may be transferred to the hardware resources 1100 fromany combination of the peripheral devices 1104 or the databases 1106.Accordingly, the memory of processors 1110, the memory/storage devices1120, the peripheral devices 1104, and the databases 1106 are examplesof computer-readable and machine-readable media.

Generally, the term “circuitry” as used in this document refers to, ispart of, or includes hardware components such as an electronic circuit,a logic circuit, a processor (shared, dedicated, or group) and/or memory(shared, dedicated, or group), an Application Specific integratedCircuit (ASIC), a field-programmable device (FPD) (e.g., afield-programmable gate array (FPGA), a programmable logic device (PLD),a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, ora programmable SoC), digital signal processors (DSPs), etc., that areconfigured to provide the described functionality. In some embodiments,the circuitry may execute one or more software or firmware programs toprovide at least some of the described functionality. The term“circuitry” may also refer to a combination of one or more hardwareelements (or a combination of circuits used in an electrical orelectronic system) with the program code used to carry out thefunctionality of that program code. In these embodiments, thecombination of hardware elements and program code may be referred to asa particular type of circuitry.

The term “processor circuitry” as used in this document refers to, ispart of, or includes circuitry capable of sequentially and automaticallycarrying out a sequence of arithmetic or logical operations, orrecording, storing, and/or transferring digital data. The term“processor circuitry” may refer to one or more application processors,one or more baseband processors, a physical central processing unit(CPU), a single-core processor, a dual-core processor, a triple-coreprocessor, a quad-core processor, and/or any other device capable ofexecuting or otherwise operating computer-executable instructions, suchas program code, software modules, and/or functional processes. Theterms “application circuitry” and/or “baseband circuitry” may beconsidered synonymous to, and may be referred to as, “processorcircuitry.”

The term “interface circuitry” as used in this document refers to, ispart of, or includes circuitry that enables the exchange of informationbetween two or more components or devices. The term “interfacecircuitry” may refer to one or more hardware interfaces, for example,buses, I/O interfaces, peripheral component interfaces, networkinterface cards, and/or the like.

The term “user equipment” or “UE” as used in this document refers to adevice with radio communication capabilities and may describe a remoteuser of network resources in a communications network. The term “userequipment” or “UE” may be considered synonymous to, and may be referredto as, client, mobile, mobile device, mobile terminal, user terminal,mobile unit, mobile station, mobile user, subscriber, user, remotestation, access agent, user agent, receiver, radio equipment,reconfigurable radio equipment, reconfigurable mobile device, etc.Furthermore, the term “user equipment” or “UE” may include any type ofwireless/wired device or any computing device including a wirelesscommunications interface.

The term “network element” as used in this document refers to physicalor virtualized equipment and/or infrastructure used to provide wired orwireless communication network services. The term “network element” maybe considered synonymous to and/or referred to as a networked computer,networking hardware, network equipment, network node, router, switch,hub, bridge, radio network controller, RAN device, RAN node, gateway,server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used in this document refers to any typeinterconnected electronic devices, computer devices, or componentsthereof. Additionally, the term “computer system” and/or “system” mayrefer to various components of a computer that are communicativelycoupled with one another. Furthermore, the term “computer system” and/or“system” may refer to multiple computer devices and/or multiplecomputing systems that are communicatively coupled with one another andconfigured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used in thisdocument refers to a computer device or computer system with programcode (e.g., software or firmware) that is specifically designed toprovide a specific computing resource. A. “virtual appliance” is avirtual machine image to be implemented by a hypervisor-equipped devicethat virtualizes or emulates a computer appliance or otherwise isdedicated to provide a specific computing resource.

The term “resource” as used in this document refers to a physical orvirtual device, a physical or virtual component within a computingenvironment, and/or a physical or virtual component within a particulardevice, such as computer devices, mechanical devices, memory space,processor/CPU time, processor/CPU usage, processor and acceleratorloads, hardware time or usage, electrical power, input/outputoperations, ports or network sockets, channel/link allocation,throughput, memory usage, storage, network, database and applications,workload units, and/or the like. A “hardware resource” may refer tocompute, storage, and/or network resources provided by physical hardwareelement(s). A “virtualized resource” may refer to compute, storage,and/or network resources provided by virtualization infrastructure to anapplication, device, system, etc. The term “network resource” or“communication resource” may refer to resources that are accessible bycomputer devices/systems via a communications network. The term “systemresources” may refer to any kind of shared entities to provide services,and may include computing and/or network resources. System resources maybe considered as a set of coherent functions, network data objects orservices, accessible through a server where such system resources resideon a single host or multiple hosts and are clearly identifiable.

The term “channel” as used in this document refers to any transmissionmedium, either tangible or intangible, which is used to communicate dataor a data stream. The term “channel” may be synonymous with and/orequivalent to “communications channel,” “data communications channel,”“transmission channel,” “data transmission channel,” “access channel,”“data access channel,” “link,” “data link,” “carrier,” “radiofrequencycarrier,” and/or any other like term denoting a pathway or mediumthrough which data is communicated. Additionally, the term “link” asused in this document refers to a connection between two devices througha RAT for the purpose of transmitting and receiving information.

The terms “instantiate,” “instantiation,” and the like as used in thisdocument refers to the creation of an instance. An “instance” alsorefers to a concrete occurrence of an object, which may occur, forexample, during execution of program code.

The terms “coupled,” “communicatively coupled,” along with derivativesthereof are used in this document. The term “coupled” may mean two ormore elements are in direct physical or electrical contact with oneanother, may mean that two or more elements indirectly contact eachother but still cooperate or interact with each other, and/or may meanthat one or more other elements are coupled or connected between theelements that are said to be coupled with each other. The term “directlycoupled” may mean that two or more elements are in direct contact withone another. The term “communicatively coupled” may mean that two ormore elements may be in contact with one another by a means ofcommunication including through a wire or other interconnect connection,through a wireless communication channel or ink, and/or the like.

The term “information element” refers to a structural element containingone or more fields. The term “field” refers to individual contents of aninformation element, or a data element that contains content. The term“SMTC” refers to an SSB-based measurement timing configurationconfigured by SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS/PBCH block. The term “a “Primary Cell”refers to the MCG cell, operating on the primary frequency, in which theUE either performs the initial connection establishment procedure orinitiates the connection re-establishment procedure. The term “PrimarySCG Cell” refers to the SCG cell in which the UE performs random accesswhen performing the Reconfiguration with Sync procedure for DCoperation. The term “Secondary Cell” refers to a cell providingadditional radio resources on top of a special cell for a UE configuredwith CA. The term “Secondary Cell Group” refers to the subset of servingcells comprising the PSCell and zero or more secondary cells for a UEconfigured with DC, The term “Serving Cell” refers to the primary cellfor a UE in RRC_CONNECTED not configured with CA/DC there is only oneserving cell comprising of the primary cell. The term “serving cell” or“serving cells” refers to the set of cells comprising the SpecialCell(s) and all secondary cells for a UE in RRC_CONNECTED configuredwith CA. The term “Special Cell” refers to the PCell of the MCG or thePSCell of the SCG for DC operation; otherwise, the term “Special Cell”refers to the Pcell.

FIGS. 12-16 show example embodiments of the systems of FIGS. 1-11 thatare configured to support extended BCH RACH resource configurations forinter-relay node discovery and measurements. More specifically, FIGS.12-16 show examples of systems described previously in relation to FIGS.1-11 that are configured for STC and SMTC configurations for IAB-node tosupport inter-IAB-node discovery and measurement.

Turning to FIG. 12, a diagram is shown illustrating an example of anintegrated access and backhaul (IAB) network 1200 including IABnode-clusters 1202 and 1204. In the IAB network 1200, the IAB-clusters1202 and 1204 each include several geographical closely deployedIAB-nodes. For example, IAB cluster 1202 consists of nodes 1202 a, 1202b, and 1202 c. For example, IAB cluster 1204 consists of nodes 1204 a,1204 b, and 1204 c. Generally, clusters 1202 and 1204 are distributedquite distant from each other. For example, distance D1 shown in FIG. 12represents a very long distance (e.g., miles or hundreds of miles) withrespect to the distance between and among the nodes of each cluster1202, 1204. For example, the distances among the nodes 1202 a, 1202 b,and 1202 c are negligible relative to the distance D1. Similarly, thedistances among the nodes 1204 a, 1204 b, and 1204 c are negligiblerelative to distance D1.

Generally, each IAB node 1202 a-c and 1204 a-c is configured to discoverand measure other IAB nodes in the same cluster. More specifically, eachof nodes 1202 a and 1204 a are respectively configured to discover andmeasure nodes 1202 b-c and nodes 1204 b-c, respectively. The remainingnodes in each cluster 1202 and 1204 operate in a similar manner.Generally, each node 1202 a-c does not need to measure IAB nodes fromother clusters such as 1204. Similarly, each node 1204 a-c does not needto measure IAB nodes from other clusters such as 1202.

FIG. 13 is a timing diagram showing example measurement timingconfigurations 1300 for inter-IAB discovery and measurement, such as forthe clusters 1202 and 1204 of FIG. 12. Specifically, three timelines areshown. Timeline 1302 represents activity of nodes 1202 a and 1204 a ofclusters 1202 and 1204. Timeline 1304 represents activity of nodes 1202b and 1204 b of clusters 1202 and 1204. Timeline 1306 representsactivity of nodes 1202 c and 1204 c of clusters 1202 and 1204. Timelines1302, 1304, and 1306 are shown in parallel to one another. In otherwords, blocks on the timelines 1302, 1304, and 1306 that are alignedwith one another represent simultaneous activity or near-simultaneousactivity. Blocks 1308 represent SSB for Access/Child BH Link. Blocks1310 represent STC for Inter-IAB Node Discovery/Measurement. Blocks 1312represent SMTC for Inter-IAB Node Discovery/Measurement.

Generally, each IAB node 1202 a-c and 1204 a-c is configured with asingle STC and multiple SMTC configurations for inter-IAB discovery andmeasurement. Additionally, each node 1202 a-c and 1204 a-c is configuredwith SSB configurations for LTE initial access. Specifically, inIAB-cluster 1202, STB-TCs with a format described below in relation toFIG. 16 for each of IAB nodes 1202 a-c are time orthogonal so that theycan be detected by each other. In other words, blocks 1310 of FIG. 13are staggered such that each node 1202 a-c and 1204 a-c of clusters 1202and 1204 are configured for STC at different time periods along timelines 1302, 1304, and 1306.

Generally, two nodes of the clusters 1202, 1204 are configured asSSB-MTCs with the format subsequently described in relation to FIG. 16.Configuration of the nodes as SSB-MTCs enables a given IAB-node 1202 ain a cluster 1202 to detect the other two IAB-nodes 1202 b-c in the samecluster. The systems previously described can configure cluster 1204 ina similar manner as cluster 1202. Because the two IAB-clusters 1202 and1204 are a relatively large distance D1 from each other, the SSB-STCsand SSB-MTCs for IAB-nodes 1202 a-c can be reused for IAB-nodes 1204a-c. Generally, a periodicity of SSB-TC and SSB-MTC for inter-IAB nodemeasurements is larger than that of SSBs for UE initial cell search.

The clusters 1202 and 1204 can be configured according to one or more ofthe following embodiments. In an example, a system (such as a systemdescribed in relation to FIGS. 1-11) can be configured for organizing,operating within, or communicating with one or more IAB clusters,wherein individual IAB clusters include a plurality of geographicallyclosely deployed IAB-nodes and may be separated from other IAB clustersby a significant distance (such as miles, hundreds of miles, orthousands of miles). In an example, the system can configure an IAB nodeof a first IAB cluster (e.g., node 1202 a of cluster 1202). The node1202 a can be configured for performing discovery and/or measurementoperations to discover and/or measure signals from one or more other IABnodes (e.g., nodes 11202 b-c) in the first IAB cluster 1202. Generally,the system can configured the first IAB node 1202 a to restrictperformance of the discovery and/or measurement operations to discoverand/or measure signals only from other IAB nodes 1202 b-c of the firstIAB cluster 1202

In some implementations, system configures an IAB node of a first IABcluster of the plurality of IAB clusters to performdiscovery/measurement operations with respect to IAB nodes in the firstIAB cluster and to exclude, from consideration within thediscovery/measurement operations, signals from IAB nodes in IAB clustersother than the first IAB cluster. In some implementations, the systemconfigures node 1202 a or any other IAB node (or each IAB node) in theIAB network to discover and measure only IAB nodes in the same cluster.In other words, the IAB node need not be configured to measure other IABnodes from a different cluster, such as cluster 1204.

In some implementations, the nodes 1202 a-c can be configured by thesystem to execute STC/SMTC as shown in FIG. 13. Generally, the system isconfigured to configure an IAB node with a single STC and multiple SMTCconfigurations for inter-IAB discovery and measurement in addition toSSB configurations for UE initial access.

In some implementations, cluster 1202 can be configured in accordancewith timelines 1302, 1304, and 1306 of FIG. 13, and the STB-TCs with theformat subsequently described in relation to FIG. 16 of nodes 1202 a-care time orthogonal so that the nodes 1202 a-c are detected by oneother. Generally, the nodes 1202 a-c (or any other node of FIG. 12) canbe configured with an IE as subsequently described in relation to FIG.16.

In some implementations, nodes 1202 a-c or 1204 a-c of clusters 1202and/or 1204 are configured by a system of FIGS. 1-11 to include twoconfigured SSB-MTCs with a format described in relation to FIG. 16. Thesystem thus is configured to enable an IAB-node to detect the other twoIAB-nodes in the same cluster. Generally, SSB-STCs and SSB-MTCs forIAB-nodes in IAB-cluster 1202 can be reused for IAB-nodes in IAB-cluster1204, given the distance D1 between the clusters. Generally, the systemconfigures, for these nodes 1202 a-c, a periodicity of SSB-TC andSSB-MTC for inter-IAB node measurements to be larger than that of SSBsfor UE initial cell search.

FIG. 14 is a diagram illustrating an example of an IAB network 1400including an IAB node-cluster 1402. In the IAB network 1400, the IABcluster 1404 includes a relatively large number of IAB nodes (e.g., 7IAB nodes). However, the number of nodes can vary and is generallygreater than 3. The IAB-nodes of cluster 1402 can include node 1402 a,1402 b, 1402 c, 1402 d, 1402 e, 1402 f, and 1402 g (hereinafter 1402a-g). In this particular configuration of cluster 1402, node 1402 g isin the center of the cluster. Node 1402 g is close to all other IABnodes 1402-af in the cluster 1402. As such, it is beneficial forIAB-node 1402 g to measure all other IAB nodes 1402 a-f in a relativelymore frequent manner than the other nodes 1402 a-f measure one another.

Generally, the IAB nodes 1402 a-f in the outer layer of the cluster 1402can be divided into two groups (represented as different patterns). Incluster 1402, IAB node 1402 a, 1402 c, and 1402 e are in a first group,and IAB-nodes 1402 b, 1402 d, and 1402 f are in a second group. Eachnode 1402 a, 1402 c, and 1402 e in the first group has two neighbornodes in the second group. All the nodes within a group are relativelymore distant from each other than each node of that group is from theneighboring nodes from the other group. Thus, the system configuresinter-group, inter-IAB nodes measurement to be performed more frequentlythan the measurement performed for inner-group inter-IAB nodemeasurement.

FIG. 15 shows a timing diagram 1500 including example measurement timingconfigurations for inter-IAB discovery and measurement in the exampleIAB-node duster 1402 of FIG. 14. More specifically, timeline 1502represents actions of node 1402 g. Timeline 1504 represents actions ofnodes 1402 a, 1402 c, and 1402 e, the first group of nodes described inrelation to FIG. 14. Timeline 1506 represents actions of nodes 1402 b,1402 d, and 1402 f, the nodes of the second group described in relationto FIG. 14. Additionally, timelines 1508, 1510, and 1512 represent theactions of node pairs including a node from each of the first and secondgroups. For example, timeline 1508 represents the actions of nodes 1402a and 1402 b. Timeline 1510 represents the actions of nodes 1402 c and1402 d. Timeline 1512 represents the actions of nodes 1402 e and 1402 f.

Each of timelines 1502, 1504, 1506, 1508, 1510, and 1512 are representedin parallel to one another, so actions represented by blocks on thetimelines that are vertically aligned represent simultaneous ornear-simultaneous execution of those actions. Blocks 1514 on thetimelines represent SSB for Access and/or a child BH link. Blocks 1516on the timelines represent STC for close inter-IAB node discovery and/ormeasurement. Blocks 1518 on the timelines represent STC for farinter-IAB node discovery and/or measurement. Blocks 1520 on thetimelines represent SMTC for close inter-IAB node discovery and/ormeasurement. Blocks 1522 represent SMTC for far inter-IAB node discoveryand/or measurement.

The SSB-TC and SSB-MTC configurations for each IAB node are described asfollows. For node 1402 g, the system configures the node for one SSBconfiguration with periodicity T1 for UE or IAB-MT initial cell search.The node 1402 g is configured for one SSB-TC configuration withperiodicity T2 for inter-IAB discovery/measurement. The node isconfigured for two SSB-MTC configurations with periodicity T2, namelySSB-MTC#1 and SSB-MTC#2, for measuring inter-group IAB nodes in thecluster. In this example, the node 1402 g includes SSB-MTC#1 formeasuring nodes 1402 a, 1402 c, and 1402 e (group 1). Similarly, node1402 g includes SSB-MTC#2 for measuring nodes 1402 b, 1402 d, and 1402 f(group 2).

In addition, node 1402 a is configured by the system as described, Node1402 a (and other nodes of group 1) include one SSB configuration withperiodicity T1 for UE or IAB-MT initial cell search. Node 1402 a (and/ornodes 1402 c and 1402 e) include two SSB-TC configurations withdifferent periodicities for inter-IAB discovery and/or measurement. Node1402 a (and/or nodes 1402 c and 1402 e) include SSB-TC#1 (in red) withperiodicity T2 for inter-group inter-IAB (namely, nodes 1402 b, 1402 d,1402 f, and 1402 g) discovery and/or measurement. Node 1402 a (and/ornodes 1402 c and 1402 e) include SSB-TC#2 with periodicity T3 forinner-group inter-IAB (namely, the other nodes of group 1) discoveryand/or measurement. For node 1402 a, this includes nodes 1402 c and 1402e, as previously described. Node 1402 a includes two pairs of SSB-MTCconfigurations with different periodicities for measuring the IAB nodesin the cluster 1402. In this example, the 1st pair of SSB-MTCs has aperiodicity T2. SSB-MTC#1 is for measuring node 1402 g, and SSB-MTC#2for measuring the nodes of group 2, including nodes 1402 b, 1402 d, and1402 f. Node 1402 a includes a 2nd pair of SSB-MTCs with periodicity T3within the group. Here, SSB-MTC#3 is for measuring node 1402 c, andSSB-MTC#4 is for measuring 1402 e.

Generally, the other nodes, namely nodes 1402 b-f have similarconfigurations as node 1402 a. For example, the inter and intra groupconfigurations are similar as for 1402 a, but are staggered on thetimelines 1502, 1504, 1506, 1508, 1510, and 1512 so that the duplexconstraint is satisfied.

The configuration of the nodes 1402 a-g as described in relation toFIGS. 14-15 can be configured according to one or more of the followingembodiments. A process can include organizing, operating within, orcommunicating with an IAB cluster that includes a plurality of IABnodes, wherein the plurality is, for example, seven. In someimplementations, the plurality can include the nodes 1402 a-g describedin relation to FIGS. 14-15. Generally, node 1402 g is in a center of theIAB cluster 1402 and close (e.g., adjacent) to all other IAB nodes 1402a-f in the cluster. Generally, node 1402 g is configured to measure allother IAB nodes 1402 a-f more frequently as compared to measurementsfrom the other IAB nodes are received. Generally, IAB nodes 1402 a-f inan outer layer of the cluster are divided into at least two groups. TheIAB nodes of a first group (for example, the nodes 1402 a, 1402 c, and1402 e) of the at least two groups are disposed in an alternatingsequence with IAB nodes of a second group (for example, the nodes 1402b, 1402 d, and 1402 e) of the at least two groups.

In some implementations, an IAB node in one group has two neighbor nodesin another group, and all the nodes within a group are relatively morefar from each other. Generally, an inter-group inter-IAB nodemeasurement can be performed in relatively more frequent manner thanthat performed for intra-group inter-IAB node measurement. Generally, asystem (e.g., described in relation to one or more of FIGS. 1-11) isconfigured to configure node 1402 g with SSB-TC and SSB-MTC (e g., asdescribed in relation to FIG. 15). Generally, configuring node 1402 gincludes providing: one SSB configuration with periodicity T1 for UE orIAB-MT initial cell search; one SSB-TC configuration with periodicity T2for inter-IAB discovery/measurement; or two SSB-MTC configurations withperiodicity T2 (e.g., SSB-MTC#1 for measuring nodes 1402 a, 1402 c, and1402 e and SSB-MIC#2 for measuring nodes 1402 b, 1402 d, and 1402 f) formeasuring inter-group IAB nodes in the cluster.

Generally, the system is configured to configure node 1402 a (or one ofeach of the other nodes 1402 b-f) with SSB-TC and SSB-MTC (e.g., asshown in FIG. 15), Generally, configuring a node 1402 a-f of the cluster1402 comprises providing: one SSB configuration with periodicity T1 forUE or IAB-MT initial cell search; two SSB-TC configurations withdifferent periodicities for inter-IAB discovery/measurement; or two pairof SSB-MTC configurations with different periodicities for measuring theIAB nodes in the cluster. In some implementations, the configuring ofone or more of the nodes 1402 a-f includes providing two SSB-TCconfigurations with different periodicities for inter-IAB discoveryand/or measurement. In some implementations, the configuration includesSSB-TC#1 with periodicity T2 for inter-group inter-IAB (e.g., nodes 1402b, 1402 d, 1402 f, and 1402 g with respect to node 1402 a) for discoveryand/or measurement or SSB-TC#2 with periodicity T3 for inner-groupinter-IAB (e.g., nodes 1402 c and 1402 e with respect to node 1402 a)discovery/measurement).

In some implementations, configuring one of the nodes 1402 a-f includesproviding two pair of SSB-MTC configurations with differentperiodicities for measuring the IAB nodes in the cluster 1400. The 1stpair of SSB-MTCs is provided with periodicity T2, such as SSB-MTC#1 formeasuring 1402 g and SSB-MTC#2 provided for measuring nodes 1402 b, 1402d, and 1402 f. The 2nd pair of SSB-MTCs is provided with periodicity T3,such as SSB-MTC#3 for measuring node 1402 c and SSB-MTC#4 for measuringnode 1402 e.

In some implementations, node 1402 a ((as shown in FIGS. 14-15) isconfigured as follows. Node 1402 a is configured for one SSBconfiguration with periodicity T1 for UE or IAB-MT initial cell search.Node 1402 a is configured for two SSB-TC configurations with differentperiodicities for inter-IAB discovery/measurement. Node 1402 a isconfigured for SSB-TC#1 with periodicity T2 for inter-group inter-IAB(e.g., nodes 1402 b, 1402 d, 1402 f, and node 1402 g) for discoveryand/or measurement. Node 1402 a is configured for SSB-TC#2 withperiodicity T3 for inner-group inter-IAB (e.g., nodes 1402 c and 1402 e)for discovery and/or measurement of those nodes. Node 1402 a isconfigured for two pair of SSB-MTC configurations with differentperiodicities for measuring the IAB nodes in the cluster. The 1st pairof SSB-MTCs with periodicity T2 includes SSB-MTC#1 for measuring 1402 gand SSB-MTC#2 for measuring nodes 1402 b, 1402 d, and 1402 f. The 2ndpair of SSB-MTCs with periodicity T3 includes SSB-MTC#3 for measuringnode 1402 c and SSB-MTC#4 for measuring node 1402 e.

Generally, the other nodes (e.g., nodes 1402 b-f of FIG. 14) areconfigured with STCs and SMTCs in similar manner as node 1402 a.

FIG. 16 is a diagram showing definitions for a SSB-TC-Access, aSSB-TC-interIAB, and a SSB-MTC-InterIAB information element. Theseconfigurations can be used in the nodes of FIGS. 12-15 as previouslydescribed.

In this embodiment, information elements SSB-TC-Access, SSB-TC-InterIABand SSB-MTC-InterIAB can be defined as follows to support UE initialcell search, inter-IAB discovery and measurement.

SSB-TC-Access is used to define the SSB transmission configuration ofIAB-DU for UE initial cell search. The format of SSB-TC-Access can bedesigned as follows.

As shown in block 1602, the SSB-TC-Access is defined by a sequence inwhich the periodicity and offset delay is chosen from a list. Theperiodicity and offset defines the periodicity and subframe offset forthe SSB transmission used for LIE access link, and the sfn denotes nsubframes. The duration defines the SSB window duration in terms ofnumber of subframes. The value for sf5 is between 0 and 4, the value forsf10 is between 0 and 9, the value of sf20 is between 0 and 19, thevalue of sf40 is between 0 and 39, the value of sf80 is between 0 and79, and the value of sf160 is between 0 and 159. The duration isenumerated for sf1, sf2, sf3, sf4, and sf5.

The SSB-TC-InterIAB is used to define the SSB transmission configurationof IAB-DU for inter-IAB node discovery and measurement. The format ofSSB-TC-InterIAB can be designed as shown in block 1604. Generally, theperiodicity and offset defines the periodicity and subframe offset forthe SSB transmission used for inter-IAB node discovery and measurement,and sfn denotes n subframes. In this example, the periodicity of SSBtransmission ranges from 80 ms to 1280 ms. Donor gNB can select theperiodicity of IAB-DU by taking into account the characteristics ofbackhaul channel dynamics. Duration defines the SSB window duration interms of number of subframes. Here, the value for sf80 is between 0 and79, the value for sf160 is between 0 and 159, the value for sf320 isbetween 0 and 319, the value for sf640 is between 0 and 639, and thevalue for sf1280 is between 0 and 1279. The duration is enumerated forsf1, sf2, sf.3, sf4, and sf5.

The SSB-MTC-InterIAB is used to define the SSB measurement timingconfiguration of IAB-DU for measuring the neighbor IAB nodes. The formatof SSB-MTC-InterIAB can be designed as shown in block 1606. Generally,periodicity and offset defines the periodicity and subframe offset formeasuring the SSB transmission from neighbor IAB nodes, and sfn denotesn subframes. Duration defines the SSB window duration in terms of numberof subframes. Pci-List defines a list of physical-cell IDs and/or IAB-DUnode IDs depending on the initialization value for SSBs. Here, the valuefor sf80 is between 0 and 79, the value for sf160 is between 0 and 159,the value for sf320 is between 0 and 319, the value for sf640 is between0 and 639, and the value for sf1280 is between 0 and 1279. The durationis enumerated for sf1, sf2, sf3, sf4, and sf5.

In some implementations, a system described in relation to one or moreof FIGS. 1-15 can include an information element (IE) or a method ofgenerating, transmitting, receiving, or processing the IE, wherein theIE is an SSB-TC-Access an SSB-TC-InterIAB IE, or an SSB-MTC-InterIAB IEto support UE or IAB-MT initial cell search or inter-IAB discovery andmeasurement. The IE can be any of the nodes described in relation toFIGS. 12-15.

Generally, the IE includes an SSB-TC-Access IE that is used to define anSSB transmission configuration of IAB-DU for UE and IAB-MT initial cellsearch. Generally, the IE including SSB-TC-Access IE is defined as shownin block 1602.

In some implementations, the IF is an SSB-TC-InterIAB IF that is todefine an SSB transmission configuration of IAB-DU for inter-IAB nodediscovery and measurement. Generally, the SSB-TC-InterIAB IE is definedas shown in block 1604 of FIG. 16. Generally, a donor gNB of the IE isconfigured to select a periodicity of IAB-DU by taking into accountcharacteristics of backhaul channel dynamics.

In some implementations, the IE includes a SSB-MTC-InterIAB IE to definean SSB measurement timing configuration of IAB-DU for measuring neighborIAB nodes. Generally, the SSB-MTC-InterIAB IE is defined as shown inblock 1606 of FIG. 16.

The following figures provide further details of systems andimplementations that may be used for various embodiments describedherein. The UEs discussed above and in the examples may generallycorrespond to UEs 101 a-b and the IABs may generally correspond toaccess nodes such as, for example, ANs 111 a-b.

FIGS. 17 and 18 are flowcharts that illustrate example processes forinter-IAB discovery and measurement. Turning to FIG. 17, a process 1700includes steps for execution by the electronic device(s), network(s),system(s), chip(s) or component(s), or portions or implementationsthereof, of FIGS. 1-11, that may be configured to perform one or moreprocesses, techniques, or methods as described herein, or portionsthereof. The process 1700 may include, at 1702, receiving a processingan The IE may be an SSB-TC-Access IE, an SSB-TC InterIAB IE, or anSSB-MTC-InterIAB IE as described in this document. For example, in someimplementations, a system described in relation to one or more of FIGS.1-15 can include an information element (IE) or a method of generating,transmitting, receiving, or processing the IE, wherein the IE is anSSB-TC-Access IE, an SSB-TC-InterIAB IE, or an SSB-MTC-InterIAB IE tosupport UE or IAB-MT initial cell search or inter-IAB discovery andmeasurement. The IE can be any of the nodes described in relation toFIGS. 12-15. Generally, the IE includes an SSB-TC-Access IE that is usedto define an SSB transmission configuration of IAB-DU for UE and IAB-MTinitial cell search. Generally, the IE including SSB-TC-Access IE isdefined as shown in block 1602. In some implementations, the IE is anSSB-TC-InterIAB IE that is to define an SSB transmission configurationof IAB-DU for inter-IAB node discovery and measurement. Generally, theSSB-TC-InterIAB IE is defined as shown in block 1604 of FIG. 16.Generally, a donor gNB of the IE is configured to select a periodicityof IAB-DU by taking into account characteristics of backhaul channeldynamics. In some implementations, the includes a SSB-MTC-InterIAB IE todefine an SSB measurement timing configuration of IAB-DU for measuringneighbor IAB nodes. Generally, the SSB-MTC-InterIAB IE is defined asshown in block 1606 of FIG. 16.

In some embodiments, the receipt/processing may be done by components ofa UE/IAB node. For example, an antenna/RIF front end of a UE/IAB mayreceive one or more configuration signals that include the IE andbaseband processing circuitry of the UE/IAB may process theconfiguration signals to determine the specific parameters defined inthe IE.

The process may further include, at step 1704, performing an initialcell search or inter-IAB discovery/measurement based on the parametersof the IE. The initial cell search may be a UE or IAB-MT initial cellsearch. In some embodiments, the UE/IAB node may reconfigure front-endcircuitry to perform the initial cell search or inter-IABdiscovery/measurement. For example, various beamforrning techniques maybe employed to directly receive signals to measure as a basis for theinitial cell search or inter-IAB discovery/measurement.

Turning to FIG. 18, a process 1800 can be executed by the device(s),network(s), system(s), chip(s) or component(s), or portions orimplementations thereof, of FIGS. 1-11. For example, the process mayinclude, at 1802, determining IAB cluster configuration information. Theinformation may configure an IAB cluster of which an IAB that performsthe process of FIG. 1800 is a part. The cluster may be a small clusterof a few IABs, or may be a large cluster with, for example, 7 or moreIABs.

The process may further include, at 1804, performingdiscovery/measurement operations based on the IAB cluster. For example,an IAB may be configured to only perform the discovery/measurementoperations to discover/measure other IABs in the same cluster. Theprocess can include performing

For one or more embodiments, at least one of the components set forth inone or more of the preceding figures may be configured to perform one ormore operations, techniques, processes, and/or methods as set forth inthe example section below. For example, the baseband circuitry asdescribed above in connection with one or more of the preceding figuresmay be configured to operate in accordance with one or more of theexamples set forth below. For another example, circuitry associated witha UE, base station, network element, etc. as described above inconnection with one or more of the preceding figures may be configuredto operate in accordance with one or more of the examples set forthbelow in the example section.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

The methods described here may be implemented in software, hardware, ora combination thereof, in different implementations. In addition, theorder of the blocks of the methods may be changed, and various elementsmay be added, reordered, combined, omitted, modified, and the like.Various modifications and changes may be made as would be obvious to aperson skilled in the art having the benefit of this disclosure. Thevarious implementations described here are meant to be illustrative andnot limiting. Many variations, modifications, additions, andimprovements are possible. Accordingly, plural instances may be providedfor components described here as a single instance. Boundaries betweenvarious components, operations and data stores are somewhat arbitrary,and particular operations are illustrated in the context of specificillustrative configurations. For purposes of explanation and notlimitation, specific details are set forth such as particularstructures, architectures, interfaces, techniques, etc. in order toprovide a thorough understanding of the various aspects of variousembodiments. However, it will be apparent to those skilled in the arthaving the benefit of the present disclosure that the various aspects ofthe various embodiments may be practiced in other examples that departfrom these specific details. In certain instances, descriptions ofwell-known devices, circuits, and methods are omitted so as not toobscure the description of the various embodiments with unnecessarydetail. For the purposes of the present document, the phrase “A or B”means (A), (B), or (A and B). Other allocations of functionality areenvisioned and may fall within the scope of claims that follow. Any ofthe above-described examples may be combined with any other example (orcombination of examples), unless explicitly stated otherwise. Theforegoing description of one or more implementations providesillustration and description, but is not intended to be exhaustive or tolimit the scope of embodiments to the precise form disclosed.Modifications and variations are possible in light of the aboveteachings or may be acquired from practice of various embodiments.

1. A method for operating a base station (BS), comprising: obtainingconfiguration data for a source integrated access and backhaul (IAB)logical radio node (gNB) of the base station, the configuration dataspecifying a timing framework for inter-relay gNB discovery andmonitoring operations, by the IAB gNB, of target IAB gNBs of a cluster;configuring the source IAB gNB, in response to obtaining theconfiguration data, for a synchronization signal block (SSB)transmission configuration (STC) window for inter-IAB gNB discovery,wherein the SSB comprises a physical broadcast channel (PBCH)transmission; configuring the source IAB gNB, in response to obtainingthe configuration data, for each target IAB gNB of the cluster, for anSSB monitoring timing configuration (SMTC) window for monitoring thattarget IAB gNB; and causing SSB transmission by the source IAB gNB inaccordance with the STC window and the SMTC window for each target IABgNB of the cluster.
 2. The method of claim 1, wherein the configurationdata specifies that the STC window of the source IAB gNB occurs at asame time as respective SMTC windows of the target IAB gNBs and eachSMTC window of the source IAB gNB occurs at the same time that anyrespective STC window occurs for the target IAB gNBs.
 3. The method ofclaim 2, wherein the STC window and each SMTC window are configuredwithin a periodicity of SSB windows for user equipment (UE) access. 4.The method of claim 1, wherein the cluster comprises three IAB gNBs,including the source IAB gNB and two target IAB gNBs, and wherein thetwo target IAB gNBs are configured using the configuration data.
 5. Themethod of claim 4, wherein the source IAB gNB of the cluster isconfigured to perform STC in a time-orthogonal manner with respect tothe target IAB gNBs of the cluster.
 6. The method of claim 4, whereinthe cluster is a first cluster, wherein a second cluster of IAB gNBs isconfigured using identical configuration data as the configuration datafor the first cluster, and wherein the method further comprises:configuring the source IAB gNB to exclude from consideration, within thediscovery and monitoring operations, signals from the IAB gNBs in thesecond cluster.
 7. The method of claim 1, wherein the STC window isconfigured in accordance with an information element indicating aperiodicity selected from a list of 80 ms, 160 ms, 320 ms, 640 ms, and1280 ms and a duration selected from a list of 1, 2, 3, 4, or 5sub-frames.
 8. The method of claim 1, wherein the SMTC window isconfigured in accordance with indicating a periodicity selected from alist of 80 ms, 160 ms, 320 ms, 640 ms, and 1280 ms and a durationselected from a list of 1, 2, 3, 4, or 5 sub-frames, and wherein theSMTC window is scheduled for each IAB gNB of the cluster.
 9. A methodfor operating a cluster of integrated access and backhaul (IAB) gNBseach corresponding to a base station (BS), the method comprising:configuring a first integrated access and backhaul (IAB) logical radionode (gNB) of the cluster for, during a first periodicity: onesynchronization signal block (SSB) transmission configuration (STC)window for inter-IAB gNB discovery, wherein the SSB comprises a physicalbroadcast channel (PBCH) transmission; and two SSB monitoring timingconfiguration (SMTC) windows for measuring inter-group IAB gNBs of thecluster; configuring a second IAB gNB of the cluster for: two STCwindows with respective periodicities for inter-IAB discovery; two pairsof SMTC windows with the respective periodicities for measuring the IABgNBs in the cluster; causing SSB transmission by the first IAB gNB inaccordance with the one STC windows and the two SMTC windows; andcausing SSB transmission by the second IAB gNB in accordance with thetwo STC windows and the two pairs of SMTC windows.
 10. The method ofclaim 9, wherein the first IAB gNB is further configured for two SSBwindows for user equipment (UE) access or initial cell search with thefirst periodicity.
 11. The method of claim 9, wherein the first IAB gNBis a neighbor to each other gNB of the cluster.
 12. The method of claim9, wherein the cluster comprises at least two groups of IAB gNBs inaddition to the first IAB gNB, wherein the second IAB gNB is included afirst group of the at least two groups of IAB gNBs.
 13. The method ofclaim 12, wherein, for the second IAB gNB, a first STC window of the twoSTC windows is configured for discovery and measurement of IAB gNBs in asecond group of the two groups of IAB gNBs, and a second STC window ofthe two STC windows is configured for discovery and measurement of otherIAB gNBs included in the first group.
 14. The method of claim 12,wherein, for the second IAB gNB, a first pair of SMTC windows of the twopairs of SMTC windows are configured for measurement of the first IABgNB and IAB gNBs in a second group of the two groups of IAB gNBs, and asecond pair of SMTC windows of the two pairs of SMTC windows areconfigured for measurement of other IAB gNBs included in the firstgroup.
 15. The method of claim 12, wherein any two IAB gNBs in a groupof the at least two groups are not neighboring IAB gNBs in the cluster.16. The method of claim 9, wherein the respective periodicities comprisethe first periodicity and a second periodicity associated with a smallerfrequency than the first periodicity.
 17. The method of claim 9, whereinan STC window is configured in accordance with an information elementindicating a periodicity selected from a list of 80 ms, 160 ms, 320 ms,640 ms, and 1280 ms and a duration selected from a list of 1, 2, 3, 4,or 5 sub-frames.
 18. The method of claim 9, wherein an SMTC window isconfigured in accordance with indicating a periodicity selected from alist of 80 ms, 160 ms, 320 ms, 640 ms, and 1280 ms and a durationselected from a list of 1, 2, 3, 4, or 5 sub-frames, and wherein theSMTC window is scheduled for each IAB gNB of the cluster.
 19. A basestation (BS), comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe one or more processors to perform operations comprising: obtainingconfiguration data for a source integrated access and backhaul (IAB)logical radio node (gNB) of the base station, the configuration dataspecifying a timing framework for inter-relay gNB discovery andmonitoring operations, by the IAB gNB, of target IAB gNBs of a cluster;configuring the source IAB gNB, in response to obtaining theconfiguration data, for a synchronization signal block (SSB)transmission configuration (STC) window for inter-IAB gNB discovery,wherein the SSB comprises a physical broadcast channel (PBCH)transmission; configuring the source IAB gNB, in response to obtainingthe configuration data, for each target IAB gNB of the cluster, for anSSB monitoring timing configuration (SMTC) window for monitoring thattarget IAB gNB; and causing SSB transmission by the source IAB gNB inaccordance with the STC window and the SMTC window for each target IABgNB of the cluster.
 20. (canceled)
 21. The base station of claim 19,wherein the configuration data specifies that the STC window of thesource IAB gNB occurs at a same time as respective SMTC windows of thetarget IAB gNBs and each SMTC window of the source IAB gNB occurs at thesame time that any respective STC window occurs for the target IAB gNBs.